Clear shared context. Useful for starting fresh.
AI agents call clear_shared_context to permanently remove resources in Blender Mcp Enhanced — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call clear_shared_context doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Blender Mcp Enhanced is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Clear shared context. Useful for starting fresh. It is categorised as a Destructive tool in the Blender Mcp Enhanced MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blender Mcp Enhanced MCP server in PolicyLayer and add a rule for clear_shared_context: 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 Blender Mcp Enhanced. Nothing to install.
clear_shared_context 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_shared_context 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_shared_context. 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_shared_context is provided by the Blender Mcp Enhanced MCP server (zachhandley/blender-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.