Clear the local cache of 4D documentation. This removes all cached documentation files, forcing fresh fetches on subsequent requests.
AI agents call clear_4d_docs_cache to permanently remove resources in 4D Documentation Viewer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes cached documentation files. While the data can be re-fetched (so impact is not permanent), the action itself is destructive—it wipes local state that took time to accumulate. This fits the Destructive category because it 'cannot be undone' without re-fetching.
From the tool's definition The tool description explicitly states it 'removes all cached documentation files' and 'clear' in the tool name indicates deletion. This is an irreversible operation that destroys cached data without restoration option.
Attacks that exploit this kind of access
Clear the local cache of 4D documentation. This removes all cached documentation files, forcing fresh fetches on subsequent requests. It is categorised as a Destructive tool in the 4D Documentation Viewer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 4D Documentation Viewer MCP server in PolicyLayer and add a rule for clear_4d_docs_cache: 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 4D Documentation Viewer. Nothing to install.
clear_4d_docs_cache 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 clear_4d_docs_cache 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 clear_4d_docs_cache. 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.
clear_4d_docs_cache is provided by the 4D Documentation Viewer MCP server (mesopelagique/mcp-4d-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →