AI agents call clear_workspace to permanently remove resources in Pure Data MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'clear_workspace' strongly suggests deletion or irreversible removal of patch state. Given the sibling tools (create_object, delete_object, connect_objects, disconnect_objects, set_param) operate on a mutable audio patch, clearing the workspace would destroy all current work without undo. This is irreversible data loss. Severity is high because an agent could accidentally wipe an entire composition.
From the tool's definition Tool named 'clear_workspace' with no description; contextually operates on Pure Data patches (audio/DSP objects) where clearing a workspace would irreversibly remove objects and connections created in the current session.
Documented attack patterns abuse exactly the kind of access clear_workspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pure Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_workspace:
{
"version": "1",
"default": "deny",
"hide": [
"clear_workspace"
]
}clear_workspace 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_workspace. It is categorised as a Destructive tool in the Pure Data MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pure Data MCP Server MCP server in PolicyLayer and add a rule for clear_workspace: 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 Pure Data MCP Server. Nothing to install.
clear_workspace 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_workspace 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_workspace. 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_workspace is provided by the Pure Data MCP Server MCP server (nikmaniatis/pd-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pure Data MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Pure Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.