Agent skill

MCP Gateway Security

MCP gateway security patterns, token management, request validation, and audit logging for MCP communications

Apache-2.0Auto-check passedSecurity

Install MCP Gateway Security

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-security -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-security --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/mcp-gateway-security .claude/skills/mcp-gateway-security && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "mcp-gateway-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security into .claude/skills/mcp-gateway-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-security", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-security -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-security --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/mcp-gateway-security .agents/skills/mcp-gateway-security && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mcp-gateway-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security into .agents/skills/mcp-gateway-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-security", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-security -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-security --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/mcp-gateway-security .cursor/skills/mcp-gateway-security && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mcp-gateway-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security into .cursor/skills/mcp-gateway-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-security", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Hack23/cia.git --path .github/skills/mcp-gateway-security

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-security -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-security --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/mcp-gateway-security .gemini/skills/mcp-gateway-security && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mcp-gateway-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security into .gemini/skills/mcp-gateway-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-security", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-security

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-security -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/mcp-gateway-security .github/skills/mcp-gateway-security && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mcp-gateway-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security into .github/skills/mcp-gateway-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-security", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-security -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-security --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/mcp-gateway-security .opencode/skills/mcp-gateway-security && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mcp-gateway-security" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-security into .opencode/skills/mcp-gateway-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-security", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mcp-gateway-security
GitHub stars: 239
Token cost: ~2.4k tokens
SKILL.md length: 525 words
Files: 1
Skills in repo: 78
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

MCP gateway security patterns, token management, request validation, and audit logging for MCP communications

Tasks that involve MCP servers
SKILL.md covers Purpose, When to Use This Skill, Threat Model for MCP and Token Management, plus 6 more sections
Needs GITHUB_TOKEN
Tasks that involve Threat modeling

What it does

MCP Gateway Security is an agent skill from Hack23/cia. MCP gateway security patterns, token management, request validation, and audit logging for MCP communications

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering MCP servers and Threat modeling. It works with Model Context Protocol. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.

When your agent uses it

Tasks that involve MCP servers
Tasks that involve Threat modeling

Example prompts

“/mcp-gateway-security”

Requirements

A credential in GITHUB_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit 6a9797b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- modelcontextprotocol.io
- owasp.org
- docs.github.com
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

MCP Gateway Security loads about 2.4k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 525 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~33
When it runs · the whole SKILL.md, loaded when a task matches: ~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Hack23/cia at commit 6a9797b, republished under its Apache-2.0 licence (© Hack23). 525 words, ~2,388 tokens.

Download SKILL.mdSave it as .claude/skills/mcp-gateway-security/SKILL.md (or your agent's skills folder).

name: mcp-gateway-security
description: MCP gateway security patterns, token management, request validation, and audit logging for MCP communications
license: Apache-2.0

MCP Gateway Security Skill

Purpose

This skill provides security patterns and best practices for securing MCP (Model Context Protocol) gateway communications in the CIA platform. It covers token management, request validation, audit logging, and threat mitigation for AI-assisted development workflows.

When to Use This Skill

Apply this skill when:

✅ Hardening MCP gateway configurations
✅ Managing tokens and credentials for MCP servers
✅ Implementing request validation for MCP tool calls
✅ Setting up audit logging for MCP communications
✅ Conducting security reviews of MCP configurations
✅ Responding to security incidents involving MCP
✅ Assessing risks of new MCP server integrations

Do NOT use for:

❌ Initial MCP setup (use mcp-gateway-configuration)
❌ Application-level security (use secure-code-review)
❌ Infrastructure security (use security-architecture-validation)

Threat Model for MCP

Attack Surface

┌──────────────────────────────────────────────┐
│                 Threat Vectors                │
├──────────────────────────────────────────────┤
│                                              │
│  ┌──────────┐    ┌──────────┐    ┌────────┐ │
│  │ Token     │    │ Prompt   │    │ Supply │ │
│  │ Theft     │    │ Injection│    │ Chain  │ │
│  └────┬─────┘    └────┬─────┘    └───┬────┘ │
│       │               │              │       │
│       ▼               ▼              ▼       │
│  ┌─────────────────────────────────────────┐ │
│  │         MCP Gateway                      │ │
│  └────┬────────────┬────────────┬──────────┘ │
│       │            │            │            │
│  ┌────▼────┐  ┌────▼────┐  ┌───▼─────┐     │
│  │ Unauth  │  │ Data    │  │ Lateral │     │
│  │ Access  │  │ Exfil   │  │ Movement│     │
│  └─────────┘  └─────────┘  └─────────┘     │
└──────────────────────────────────────────────┘

Threat Matrix

Threat	Likelihood	Impact	Mitigation
Token theft from config	Medium	Critical	Environment variables, secret managers
Prompt injection via tools	Medium	High	Input validation, output sanitization
Supply chain attack on MCP packages	Low	Critical	Version pinning, integrity checks
Unauthorized file access	Medium	High	Directory restrictions, least privilege
Data exfiltration via MCP tools	Low	High	Output monitoring, allowed destinations
Privilege escalation	Low	Critical	Role-based access, capability limits

Token Management

Token Security Requirements

Requirement	Implementation	Priority
No hardcoded tokens	Environment variables only	Critical
Token rotation	Regular rotation schedule	High
Least privilege scopes	Minimal required permissions	Critical
Token encryption at rest	OS keychain or secret manager	High
Token audit trail	Log token usage, not values	Medium

Secure Token Configuration

json

{
  "mcpServers": {
    "github": {
      "type": "stdio",
      "command": "github-mcp-server",
      "env": {
        "GITHUB_TOKEN": "${GITHUB_TOKEN}"
      }
    }
  }
}

Token Handling Rules:

✅ DO: Use environment variable references (${VAR_NAME})
✅ DO: Use GitHub Actions secrets for CI/CD tokens
✅ DO: Rotate tokens at least quarterly
✅ DO: Use fine-grained PATs with minimal scopes
✅ DO: Revoke tokens immediately when compromised

❌ DON'T: Hardcode tokens in configuration files
❌ DON'T: Commit tokens to version control
❌ DON'T: Share tokens between environments
❌ DON'T: Use classic PATs with broad scopes
❌ DON'T: Log token values in any log output

GitHub Token Scopes (Principle of Least Privilege)

MCP Operation	Required Scope	Justification
Read code	`contents:read`	Code search and file reading
Create PRs	`pull_requests:write`	PR creation and updates
Manage issues	`issues:write`	Issue creation and updates
Read workflows	`actions:read`	CI/CD status checking
Security alerts	`security_events:read`	CodeQL and Dependabot

Request Validation

Input Validation for MCP Tools

File Operations:

Validation Rules:
1. Path must be within allowed directories
2. Path must not contain traversal sequences (../)
3. File extension must be in allowed list
4. File size must not exceed limits
5. Content must not contain known malicious patterns

Code Operations:

Validation Rules:
1. Branch names must match allowed pattern
2. Commit messages must not contain secrets
3. File content must pass security scanning
4. PR descriptions must not leak sensitive data

Output Sanitization

Before Returning MCP Tool Output:
1. Strip any credential-like patterns
2. Remove internal IP addresses/hostnames
3. Truncate excessively large outputs
4. Validate JSON/structured output format
5. Log sanitization actions for audit

Show full SKILL.md (231 more words)Show less

Dangerous Tool Patterns

Tool	Risk	Mitigation
`filesystem.write_file`	Overwrite critical files	Restrict to project directories
`filesystem.delete`	Data loss	Require confirmation, backup
`github.push_files`	Inject malicious code	Code review before merge
`playwright.evaluate`	Execute arbitrary JS	Sandbox, restrict domains
`bash.execute`	System command execution	Allowlist commands, sandbox

Audit Logging

What to Log

Event	Log Level	Data to Capture
MCP server start/stop	INFO	Server name, timestamp
Tool invocation	INFO	Tool name, parameters (sanitized)
Authentication success	INFO	Server name, token type (not value)
Authentication failure	WARN	Server name, failure reason
Access denied	WARN	Tool, resource, reason
Configuration change	INFO	What changed, who changed it
Error/exception	ERROR	Error details, stack trace

What NOT to Log

❌ Token values or API keys
❌ File contents containing secrets
❌ User passwords or credentials
❌ Full request/response bodies with PII
❌ Internal network topology details

Audit Log Format

json

{
  "timestamp": "2024-01-15T10:30:00Z",
  "event": "mcp.tool.invocation",
  "server": "github",
  "tool": "create_pull_request",
  "parameters": {
    "owner": "Hack23",
    "repo": "cia",
    "title": "[REDACTED]"
  },
  "result": "success",
  "duration_ms": 1250,
  "user": "copilot-agent"
}

Security Configuration Checklist

Pre-Deployment

□ All tokens use environment variables (never hardcoded)
□ Token scopes follow least privilege
□ Filesystem access restricted to project directory only
□ MCP package versions pinned to specific releases
□ Configuration file committed (without secrets)
□ No sensitive data in MCP server arguments
□ SSE server URLs use HTTPS only
□ Certificate validation enabled for remote servers

Periodic Review (Monthly)

□ Review token scopes — remove unnecessary permissions
□ Rotate tokens per schedule
□ Check for new MCP package versions and CVEs
□ Review audit logs for anomalies
□ Verify directory restrictions still appropriate
□ Test authentication failure handling
□ Review and update threat model
□ Check for deprecated MCP server versions

Incident Response

MCP Security Incident
    │
    ├─→ Token Compromise
    │   ├─→ Revoke token immediately
    │   ├─→ Rotate all related tokens
    │   ├─→ Review audit logs for unauthorized access
    │   └─→ Update token storage mechanism
    │
    ├─→ Unauthorized File Access
    │   ├─→ Review filesystem server configuration
    │   ├─→ Check for directory traversal attempts
    │   ├─→ Restrict filesystem paths
    │   └─→ Review accessed files for data exposure
    │
    ├─→ Supply Chain Attack
    │   ├─→ Pin to known-good version
    │   ├─→ Verify package integrity
    │   ├─→ Check for malicious tool behavior
    │   └─→ Report to MCP package maintainers
    │
    └─→ Prompt Injection
        ├─→ Review tool invocation logs
        ├─→ Identify injected content
        ├─→ Assess data exposure
        └─→ Update input validation rules

OWASP Agentic Security Alignment

OWASP Agentic Risk	MCP Mitigation
Excessive Agency	Restrict tool capabilities, require confirmation
Tool Misuse	Input validation, output monitoring
Privilege Escalation	Least privilege tokens, capability limits
Data Leakage	Output sanitization, logging controls
Insecure Output	Validate all MCP tool responses
Supply Chain	Pin versions, verify integrity

ISMS Alignment

Security Area	ISO 27001	NIST CSF	CIS Controls
Token Management	A.8.24, A.5.17	PR.DS-1	CIS 3.11
Access Control	A.8.3, A.8.5	PR.AC-4	CIS 6.1
Audit Logging	A.8.15	DE.AE-3	CIS 8.2
Input Validation	A.8.28	PR.IP-12	CIS 16.1
Configuration Mgmt	A.8.9	PR.IP-1	CIS 4.1
Incident Response	A.5.24-A.5.27	RS.MA-1	CIS 17.1

References

Files

Just SKILL.md in .github/skills/mcp-gateway-security of Hack23/cia.

Open the folder on GitHubat commit 6a9797b

Compare with similar skills

MCP Gateway Security next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

MCP Gateway Security compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
MCP Gateway Security this skillHack23/cia	239	—	~2.4k	Automated safety check: Pass	Apache-2.0	today
Forensifyalexgreensh/repo-forensics	187	—	~2.5k	Automated safety check: Notes	Custom licence	10 days ago
Securing AI Systemstrilwu/secskills	156	—	~2.9k	Automated safety check: Pass	MIT	1 mo ago
Plugin Scanneriflytek/skillhub	5.2k	2 repos	~1.1k	Automated safety check: Notes	Apache-2.0	6 days ago
Webcrypt MCPputervision/state-memory-mcp	111	—	~847	Automated safety check: Pass	MIT	4 days ago
Security Passcyanheads/pubmed-mcp-server	154	—	~6.4k	Automated safety check: Pass	Apache-2.0	3 days ago

Similar skills

Forensify
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
187 GitHub stars~2.5k tokensUpdated 10 days ago
SecurityAuto-check: notes
Securing AI Systems
trilwu/secskills
Assess and harden LLM applications and agentic systems against prompt injection, tool misuse, excessive agency, memory poisoning, RAG data leakage, and model supply-chain risk, mapped to the OWASP…
156 GitHub stars~2.9k tokensUpdated 1 mo ago
SecurityAuto-check passed
Plugin Scanner
iflytek/skillhub
Scan AI agent skills, plugins, MCP servers, and agent tooling for prompt injection, unsafe commands, secret exposure, and supply-chain risks before installing or trusting them.
5.2k GitHub starsUsed in 2 repos~1.1k tokens
SecurityAuto-check: notes
Webcrypt MCP
putervision/state-memory-mcp
Teaches the agent to use the WebCrypt MCP server for AES-256-GCM symmetric encryption, RSA-4096 hybrid encryption, key generation, digital signatures, hashing, and post-quantum cryptography.
111 GitHub stars~847 tokensUpdated 4 days ago
SecurityAuto-check passed
Security Pass
cyanheads/pubmed-mcp-server
Review an MCP server for common security gaps: LLM-facing surfaces as injection vector (tools, resources, prompts, descriptions), scope blast radius, destructive ops without consent, upstream auth…
154 GitHub stars~6.4k tokensUpdated 3 days ago
SecurityAuto-check passed
Agent Bom Registry
LeoYeAI/openclaw-master-skills
MCP server security registry and trust assessment — look up servers in the 427+ server security metadata registry, run pre-install marketplace checks, batch fleet risk scoring, assess skill file…
2.2k GitHub stars~969 tokensUpdated 2 mo ago
SecurityAuto-check passed

Questions about MCP Gateway Security

What does MCP Gateway Security do?

MCP gateway security patterns, token management, request validation, and audit logging for MCP communications. MCP Gateway Security is an agent skill from Hack23/cia.

When should I use MCP Gateway Security?

MCP Gateway Security fits situations like: tasks that involve MCP servers; tasks that involve Threat modeling.

How do I install MCP Gateway Security in Claude Code?

Run `npx skills add Hack23/cia --skill mcp-gateway-security -a claude-code`. Or copy the skill folder (.github/skills/mcp-gateway-security in Hack23/cia) into .claude/skills/mcp-gateway-security in your project. Claude Code loads it when a task matches its description.

How do I install MCP Gateway Security in Codex?

Run `npx skills add Hack23/cia --skill mcp-gateway-security -a codex`. Or copy the skill folder (.github/skills/mcp-gateway-security in Hack23/cia) into .agents/skills/mcp-gateway-security in your project. Codex loads it when a task matches its description.

Can I use MCP Gateway Security in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill mcp-gateway-security -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-gateway-security, .gemini/skills/mcp-gateway-security, .github/skills/mcp-gateway-security and .opencode/skills/mcp-gateway-security in your project.

What does MCP Gateway Security need to run?

Going by SKILL.md and its folder, MCP Gateway Security needs credentials named GITHUB_TOKEN. Our summary lists: A credential in GITHUB_TOKEN.

Does MCP Gateway Security access the network?

SKILL.md names 4 domains. As links in the text: modelcontextprotocol.io, owasp.org, docs.github.com and github.com. This is read from the text; nothing was executed.

Is MCP Gateway Security safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does MCP Gateway Security use?

MCP Gateway Security is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does MCP Gateway Security use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to MCP Gateway Security?

Skills that share tags, products or a category with MCP Gateway Security: Forensify (alexgreensh/repo-forensics, 187 stars), Securing AI Systems (trilwu/secskills, 156 stars), Plugin Scanner (iflytek/skillhub, 5.2k stars) and Webcrypt MCP (putervision/state-memory-mcp, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains MCP Gateway Security?

Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.

Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install MCP Gateway Security

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

MCP Gateway Security Skill

Purpose

When to Use This Skill

Threat Model for MCP

Attack Surface

Threat Matrix

Token Management

Token Security Requirements

Secure Token Configuration

GitHub Token Scopes (Principle of Least Privilege)

Request Validation

Input Validation for MCP Tools

Output Sanitization

Dangerous Tool Patterns

Audit Logging

What to Log

What NOT to Log

Audit Log Format

Security Configuration Checklist

Pre-Deployment

Periodic Review (Monthly)

Incident Response

OWASP Agentic Security Alignment

ISMS Alignment

References

Files

Compare with similar skills

Similar skills

More from Hack23/cia

Related

Questions about MCP Gateway Security