AI agents call clear_ifc_knowledge_cache to permanently remove resources in IFC Bonsai MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'clear' in the tool name strongly suggests irreversible removal of cached IFC knowledge data. Clearing a cache cannot typically be undone, placing this in the Destructive category. However, since caches can usually be rebuilt, the severity is high rather than critical. Confidence is moderate due to the empty description.
From the tool's definition Tool name: 'clear_ifc_knowledge_cache' — 'clear' implies irreversible deletion of cached data. Description is empty, providing no additional context.
Documented attack patterns abuse exactly the kind of access clear_ifc_knowledge_cache gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IFC Bonsai MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_ifc_knowledge_cache:
{
"version": "1",
"default": "deny",
"hide": [
"clear_ifc_knowledge_cache"
]
}clear_ifc_knowledge_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.
clear_ifc_knowledge_cache. It is categorised as a Destructive tool in the IFC Bonsai MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the IFC Bonsai MCP server in PolicyLayer and add a rule for clear_ifc_knowledge_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 IFC Bonsai MCP. Nothing to install.
clear_ifc_knowledge_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_ifc_knowledge_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_ifc_knowledge_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_ifc_knowledge_cache is provided by the IFC Bonsai MCP server (show2instruct/ifc-bonsai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 52 IFC Bonsai MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
52 IFC Bonsai MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.