Remove an applied API-level policy from an API Manager API instance.
AI agents call api_policy_delete to permanently remove resources in Anypoint MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a policy from an API Manager instance is a destructive operation that cannot be automatically undone. Policies provide critical security, rate limiting, and access control functions; deleting one could expose an API to unauthorized access or remove essential protections.
From the tool's definition Tool name contains 'delete' and description states 'Remove an applied API-level policy' - this is an irreversible deletion of a policy configuration from a live API instance.
Attacks that exploit this kind of access
Remove an applied API-level policy from an API Manager API instance. It is categorised as a Destructive tool in the Anypoint MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Anypoint MCP Server MCP server in PolicyLayer and add a rule for api_policy_delete: 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 Anypoint MCP Server. Nothing to install.
api_policy_delete 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 api_policy_delete 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 api_policy_delete. 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.
api_policy_delete is provided by the Anypoint MCP Server MCP server (sravannerella/mulesoft-mcp-server). 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 →