Skip to content
AI & Agents
Skill

/mcp-security-reviewer

Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.

BOOST
From plugin
llm-agents-ecosystem-handbook
55510 skills
Install
$ npx -y skills add oxbshw/LLM-Agents-Ecosystem-Handbook --skill mcp-security-reviewer --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/mcp-security-reviewer

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.

SKILL.md

mcp-security-reviewer.SKILL.md
name: mcp-security-reviewer
description: Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.
version: 0.1.0

MCP Security Reviewer

When to use

  • A new MCP server is being added to an agent
  • An MCP server version is being bumped
  • An incident triggered a re-review

Inputs

| Name | Type | Required | Notes | |---|---|---|---| | `repo_url` | string | yes | the MCP server's source | | `version` | string | yes | tag or commit SHA being adopted | | `intended_use` | string | yes | one paragraph: what we'll let it do |

Workflow

1. **Source review**: clone at the pinned version; check for unexpected files / scripts 2. **Capabilities**: list every tool and resource exposed; map to risk levels (`references/mcp-risk-matrix.md`) 3. **Network**: identify outbound endpoints; document and assess each 4. **Permissions**: minimum required scopes / tokens; document over-permissions 5. **Output handling**: confirm the agent treats tool output as untrusted (sanitization, no execution) 6. **Approvals**: define which tools require human approval 7. **Produce filled `MCP_SERVER.md`** in `mcp/<server>.md`

References

  • [`references/mcp-risk-matrix.md`](references/mcp-risk-matrix.md)

Success criteria

  • All tools labelled by risk
  • High/Critical tools gated by approval
  • Pinned version (no `latest` / floating refs)
  • Documented network egress

Failure modes

  • Source unavailable / un-pinnable → reject
  • Discovered hidden tool not in docs → reject and report upstream
Read more
Ships withllm-agents-ecosystem-handbook

A practical operating manual for building, evaluating, securing, and shipping modern LLM agent systems. Modern agents are not "a prompt + a tool."

Get the whole plugin