Remove a previously installed library URL from the session registry.
AI agents call library_uninstall 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.
The tool irreversibly removes/uninstalls a library from the session registry. 'Remove' implies deletion that cannot be undone without re-installing, making it Destructive. Severity is medium since it affects session-scoped library registrations rather than persistent canvas data.
From the tool's definition Remove a previously installed library URL from the session registry
Attacks that exploit this kind of access
Remove a previously installed library URL from the session registry. 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 library_uninstall: 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.
library_uninstall 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 library_uninstall 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 library_uninstall. 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.
library_uninstall 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 →