Cancel an active deep research session and save its checkpoint.
AI agents call cancel_research to permanently remove resources in Local DeepWiki MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call cancel_research doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Local DeepWiki MCP Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Cancel an active deep research session and save its checkpoint. It is categorised as a Destructive tool in the Local DeepWiki MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Local DeepWiki MCP Server MCP server in PolicyLayer and add a rule for cancel_research: 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 Local DeepWiki MCP Server. Nothing to install.
cancel_research 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 cancel_research 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 cancel_research. 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.
cancel_research is provided by the Local DeepWiki MCP Server MCP server (urbandiver/local-deepwiki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.