AI agents call reclaim_clear_exceptions to permanently remove resources in Reclaim Ai MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The verb 'clear' in the context of task management systems typically means to delete or wipe out records irreversibly. While the description is empty (lowering confidence slightly), the destructive nature of clearing exceptions—data structures that track task anomalies or overrides—suggests this operation cannot be easily reversed.
From the tool's definition Tool name 'reclaim_clear_exceptions' indicates deletion or irreversible clearing of exception records. The 'clear' verb combined with 'exceptions' suggests removal of data that cannot be undone. No description provided to refine understanding.
Documented attack patterns abuse exactly the kind of access reclaim_clear_exceptions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reclaim Ai MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reclaim_clear_exceptions:
{
"version": "1",
"default": "deny",
"hide": [
"reclaim_clear_exceptions"
]
}reclaim_clear_exceptions 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.
reclaim_clear_exceptions. It is categorised as a Destructive tool in the Reclaim Ai MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reclaim Ai MCP Server MCP server in PolicyLayer and add a rule for reclaim_clear_exceptions: 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 Reclaim Ai MCP Server. Nothing to install.
reclaim_clear_exceptions 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 reclaim_clear_exceptions 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 reclaim_clear_exceptions. 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.
reclaim_clear_exceptions is provided by the Reclaim Ai MCP Server MCP server (johnjhughes/reclaim-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reclaim Ai MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Reclaim Ai MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.