AI agents invoke swarm_execute_skill to trigger actions in Mcp Swarm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers external operations (code review, document generation, and other skills) whose side effects depend entirely on which skill is selected and its arguments. This fits the Execute category: it runs operations whose consequences are task-dependent. The 'high' severity reflects that an AI agent could select and execute harmful skills if prompt-injected or misaligned.
From the tool's definition Tool name 'swarm_execute_skill' combined with description stating it 'executes specified skills (such as code review, document generation, etc.)'.
Attacks that exploit this kind of access
执行指定的技能(如代码审查、文档生成等)。. It is categorised as a Execute tool in the Mcp Swarm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Swarm MCP server in PolicyLayer and add a rule for swarm_execute_skill: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Swarm. Nothing to install.
swarm_execute_skill is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the swarm_execute_skill rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for swarm_execute_skill. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
swarm_execute_skill is provided by the Mcp Swarm MCP server (moselu/mcp-swarm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →