Delete a user-level library by name. No-op if not found.
AI agents call user_library_remove to permanently remove resources in Whiteboard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes user data (a library) without undo capability. Although the blast radius is somewhat limited to a single user's library collection rather than affecting external systems or multiple users, the irreversible nature and data destruction classify it as Destructive. The 'No-op if not found' note indicates it silently fails when the library doesn't exist, which could mask misuse.
From the tool's definition 'Delete a user-level library by name' — the tool irreversibly removes a user library from Excalidraw, destroying stored content and configurations that cannot be recovered.
Attacks that exploit this kind of access
Delete a user-level library by name. No-op if not found. It is categorised as a Destructive tool in the Whiteboard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Whiteboard MCP server in PolicyLayer and add a rule for user_library_remove: 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 Whiteboard. Nothing to install.
user_library_remove 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 user_library_remove 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 user_library_remove. 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.
user_library_remove is provided by the Whiteboard MCP server (kamiazya/whiteboard). 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 →