AI agents use swarm_generate_mr_description to create or update resources in Mcp Swarm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Swarm environment.
This tool generates (creates) template content for merge/pull request descriptions. While templates themselves are not destructive, generating and inserting content into version control documentation is a Write operation—it modifies repository metadata/documentation reversibly.
From the tool's definition Tool name 'swarm_generate_mr_description' and description '生成 Merge Request / Pull Request 描述模板' (Generate Merge Request / Pull Request description template) indicate creation of template content that would be submitted as part of a code review process.
Attacks that exploit this kind of access
生成 Merge Request / Pull Request 描述模板。. It is categorised as a Write tool in the Mcp Swarm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Swarm MCP server in PolicyLayer and add a rule for swarm_generate_mr_description: 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_generate_mr_description is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the swarm_generate_mr_description 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_generate_mr_description. 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_generate_mr_description 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 →