AI agents invoke swarm_create_dynamic_agents 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 dynamically creates and orchestrates multiple AI sub-agents based on task descriptions. Creating and launching autonomous agents constitutes execution of external operations with unpredictable, cascading effects depending on arguments. The self-organizing swarm structure amplifies blast radius — misuse could spawn many agents performing unintended actions across systems.
From the tool's definition 自动生成多个 specialized sub-agents,实现自组织结构 (automatically generates multiple specialized sub-agents, implementing self-organizing structure)
Attacks that exploit this kind of access
根据任务描述自动生成多个 specialized sub-agents,实现自组织结构(参考 Kimi K2.5 Agent Swarm)。. 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_create_dynamic_agents: 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_create_dynamic_agents 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_create_dynamic_agents 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_create_dynamic_agents. 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_create_dynamic_agents 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 →