Load user-level library metadata from ~/.excalidraw/.user-libraries/{name}.meta.json. Returns an empty manifest with revision 0 when metadata has not been created yet.
AI agents call user_library_metadata_get to retrieve information from Whiteboard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads metadata from a local file (~/.excalidraw/.user-libraries/{name}.meta.json) and returns its contents. It is a straightforward data retrieval operation with no side effects, capability to modify files, execute commands, delete data, or commit financial transactions.
From the tool's definition Tool description explicitly states 'Load user-level library metadata' and 'Returns an empty manifest', indicating retrieval of data without modification. No mutation, deletion, or execution capability is mentioned.
Attacks that exploit this kind of access
Load user-level library metadata from ~/.excalidraw/.user-libraries/{name}.meta.json. Returns an empty manifest with revision 0 when metadata has not been created yet. It is categorised as a Read tool in the Whiteboard MCP Server, which means it retrieves data without modifying state.
Register the Whiteboard MCP server in PolicyLayer and add a rule for user_library_metadata_get: 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_metadata_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the user_library_metadata_get 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_metadata_get. 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_metadata_get 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 →