user_library_metadata_delete

Delete alias / note / scale keys from a user-level library metadata manifest. Requires the current revision and returns the updated manifest with revision + 1.

Server Whiteboard kamiazya/whiteboard
Category Destructive
Risk class Critical
Parameters 00 required

What user_library_metadata_delete does on Whiteboard

AI agents call user_library_metadata_delete 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.

Why user_library_metadata_delete needs a policy

This tool irreversibly removes data (metadata keys) from a user's library manifest. While scoped to a single user's library rather than affecting production systems or having financial impact, the destructive nature of permanent deletion without undo capability places it in the Destructive category.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete alias / note / scale keys from a user-level library metadata manifest.' The action is irreversible—deleted metadata cannot be recovered without external backup.

Questions about user_library_metadata_delete

What does the user_library_metadata_delete tool do? +

Delete alias / note / scale keys from a user-level library metadata manifest. Requires the current revision and returns the updated manifest with revision + 1. 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.

How do I enforce a policy on user_library_metadata_delete? +

Register the Whiteboard MCP server in PolicyLayer and add a rule for user_library_metadata_delete: 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.

What risk level is user_library_metadata_delete? +

user_library_metadata_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit user_library_metadata_delete? +

Yes. Add a rate_limit block to the user_library_metadata_delete 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.

How do I block user_library_metadata_delete completely? +

Set action: deny in the PolicyLayer policy for user_library_metadata_delete. 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.

What MCP server provides user_library_metadata_delete? +

user_library_metadata_delete 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.