Stops mitigation for a specific IP address and removes the zone.
AI agents call remove_mitigation to permanently remove resources in A10 Guardian — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible operation by removing a zone configuration. While it also stops mitigation (a reversible state change), the zone removal aspect makes this Destructive rather than Execute or Write. In a DDoS mitigation context, removing a zone could disrupt critical protection infrastructure.
From the tool's definition Tool description states 'Stops mitigation for a specific IP address and removes the zone.' The action 'removes the zone' is irreversible data deletion.
Attacks that exploit this kind of access
Stops mitigation for a specific IP address and removes the zone. It is categorised as a Destructive tool in the A10 Guardian MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the A10 Guardian MCP server in PolicyLayer and add a rule for remove_mitigation: 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 A10 Guardian. Nothing to install.
remove_mitigation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_mitigation 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 remove_mitigation. 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.
remove_mitigation is provided by the A10 Guardian MCP server (opastorello/a10-guardian). 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 →