Delete all cached render files and report freed space. Removes every .png file from the configured cache directory. Does nothing (and still reports success) when the cache is disabled or the directory does not exist. Args: ctx: MCP context for logging Returns: Dict with success status, cleared_fi...
AI agents call clear_cache to permanently remove resources in OpenSCAD MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes cached PNG files. Although the data being deleted is non-essential cache (recoverable by re-rendering), the operation is inherently irreversible and destructive in nature. It matches the Destructive category definition as it irreversibly deletes data.
From the tool's definition Tool description explicitly states it will "Delete all cached render files" and "Removes every `.png` file from the configured cache directory." The operation is irreversible and removes data.
Documented attack patterns abuse exactly the kind of access clear_cache gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSCAD MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_cache:
{
"version": "1",
"default": "deny",
"hide": [
"clear_cache"
]
}clear_cache 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.
Delete all cached render files and report freed space. Removes every .png file from the configured cache directory. Does nothing (and still reports success) when the cache is disabled or the directory does not exist. Args: ctx: MCP context for logging Returns: Dict with success status, cleared_files count, and freed_bytes. It is categorised as a Destructive tool in the OpenSCAD MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenSCAD MCP Server MCP server in PolicyLayer and add a rule for clear_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 OpenSCAD MCP Server. Nothing to install.
clear_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_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_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_cache is provided by the OpenSCAD MCP Server MCP server (quellant/openscad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 OpenSCAD MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 OpenSCAD MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.