set_mitigation_groups
AI agents use set_mitigation_groups to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.
The tool likely creates or modifies mitigation group mappings within the Mipiti security platform—a reversible, administrative write operation. No evidence of deletion (would be Destructive), code execution (would be Execute), or financial impact (would be Financial). Classified as Write rather than Read because 'set_' implies state modification.
From the tool's definition Tool name 'set_mitigation_groups' combined with sibling tools like 'add_asset', 'add_assumption', 'add_evidence' which are clearly Write operations on a security posture management platform.
Attacks that exploit this kind of access
set_mitigation_groups. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for set_mitigation_groups: 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 Mipiti MCP Server. Nothing to install.
set_mitigation_groups 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 set_mitigation_groups 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 set_mitigation_groups. 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.
set_mitigation_groups is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-mcp). 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 →