exploit_cache_clear
Clear all cached exploit-dev results. Use when binaries have been modified or to free memory.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/exploit-cache-clear.md
What exploit_cache_clear does on Jshookmcp
AI agents call exploit_cache_clear to permanently remove resources in Jshookmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why exploit_cache_clear is rated Critical
The tool performs an irreversible operation that wipes cached exploit development results. While the blast radius is limited to cached data (not production systems), the destructive nature of clearing cache without recovery options and the potential loss of analysis results from security work places this in the Destructive category.
From the tool's definition Tool name includes 'clear' and description states 'Clear all cached exploit-dev results', indicating irreversible deletion of cached data. The action cannot be undone and represents data loss.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs exploit_cache_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For exploit_cache_clear, this is the rule to start with:
exploit_cache_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every exploit_cache_clear call is checked against it from then on.
Questions about exploit_cache_clear
Clear all cached exploit-dev results. Use when binaries have been modified or to free memory. It is categorised as a Destructive tool in the Jshookmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jshook MCP server in PolicyLayer and add a rule for exploit_cache_clear: 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 Jshookmcp. Nothing to install.
exploit_cache_clear 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 exploit_cache_clear 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 exploit_cache_clear. 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.
exploit_cache_clear is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue