exploit_cache_invalidate
Invalidate cached exploit-dev results for a specific binary (by path). Computes the binary hash and removes all matching cache entries. Call without binaryPath to clear the entire cache. Use when binaries have been recompiled or modified.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/exploit-cache-invalidate.md
What exploit_cache_invalidate does on Jshookmcp
AI agents call exploit_cache_invalidate 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_invalidate is rated Critical
This tool irreversibly removes cached data. While cache can be rebuilt, the deletion of entries is a destructive, non-reversible action. The blast radius is medium since it only affects cached exploit development results, not primary data, but misuse (especially clearing the entire cache) could disrupt ongoing work and force expensive recomputation.
From the tool's definition Invalidate cached exploit-dev results... removes all matching cache entries... clear the entire cache
Attacks that exploit this kind of access
The rule that runs exploit_cache_invalidate 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_invalidate, this is the rule to start with:
exploit_cache_invalidate 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_invalidate call is checked against it from then on.
Questions about exploit_cache_invalidate
Invalidate cached exploit-dev results for a specific binary (by path). Computes the binary hash and removes all matching cache entries. Call without binaryPath to clear the entire cache. Use when binaries have been recompiled or modified. 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_invalidate: 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_invalidate 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_invalidate 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_invalidate. 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_invalidate 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