Manage library lifecycle: add/rename/refresh/remove/info. Destructive actions require confirmation.
AI agents call manage_library to permanently remove resources in DocShark — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool spans multiple categories (Write for add/rename/refresh, Destructive for remove), so per the rules the most severe applicable category is chosen. 'Remove' on a library would irreversibly delete indexed documentation data, and the description itself flags 'Destructive actions' as a distinct concern requiring confirmation.
From the tool's definition 'remove' and 'Destructive actions require confirmation' — the tool explicitly includes destructive operations that can irreversibly delete indexed libraries from the local knowledge base.
Attacks that exploit this kind of access
Manage library lifecycle: add/rename/refresh/remove/info. Destructive actions require confirmation. It is categorised as a Destructive tool in the DocShark MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DocShark MCP server in PolicyLayer and add a rule for manage_library: 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 DocShark. Nothing to install.
manage_library 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 manage_library 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 manage_library. 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.
manage_library is provided by the DocShark MCP server (michael-obele/docshark). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
manage_library is one line of DocShark's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →