AI agents call policies.remove to permanently remove resources in Executor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a policy record identified by id and owner. Policy removal cannot be undone and affects access control or tool availability for agents/users. While not as critical as deleting user data, this is a destructive operation that warrants the Destructive category and high severity due to potential loss of security controls or operational configurations.
From the tool's definition Tool name includes 'remove' which indicates deletion. Description states 'Remove a tool policy by id + owner' — the action is irreversible deletion of a policy configuration.
Documented attack patterns abuse exactly the kind of access policies.remove gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Executor, and nothing reaches the server without passing your rules. This is the rule we recommend for policies.remove:
{
"version": "1",
"default": "deny",
"hide": [
"policies.remove"
]
}policies.remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a tool policy by id + owner. It is categorised as a Destructive tool in the Executor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Executor MCP server in PolicyLayer and add a rule for policies.remove: 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 Executor. Nothing to install.
policies.remove 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 policies.remove 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 policies.remove. 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.
policies.remove is provided by the Executor MCP server (rhyssullivan/executor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Executor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Executor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.