delete_library_group

Removes a library group. TWO MODES via cascadeMembers: (1) DEFAULT (cascadeMembers omitted/false) — DISSOLVE: member libraries are KEPT and re-appear in the standalone library card list at the position the group occupied. Safe; non-destructive. (2) cascadeMembers:true — DESTRUCTIVE: also deletes ...

Server Pinako AI Bridge teleomorph/pinako-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_library_group does on Pinako AI Bridge

AI agents call delete_library_group to permanently remove resources in Pinako AI Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_library_group needs a policy

While the default mode (cascadeMembers omitted/false) is reversible (dissolve only), the tool's primary dangerous capability is deletion with cascadeMembers:true, which irreversibly removes owned libraries from cloud and unlinks shared libraries.

From the tool's definition Tool description explicitly states 'DESTRUCTIVE: also deletes each member library (owned libraries are deleted from cloud; linked libraries are unlinked from this account)' and requires 'EXPLICIT USER APPROVAL when cascadeMembers:true'.

Questions about delete_library_group

What does the delete_library_group tool do? +

Removes a library group. TWO MODES via cascadeMembers: (1) DEFAULT (cascadeMembers omitted/false) — DISSOLVE: member libraries are KEPT and re-appear in the standalone library card list at the position the group occupied. Safe; non-destructive. (2) cascadeMembers:true — DESTRUCTIVE: also deletes each member library (owned libraries are deleted from cloud; linked libraries are unlinked from this account). REQUIRES EXPLICIT USER APPROVAL when cascadeMembers:true: set confirmedByUser:true ONLY after the user has confirmed they want to lose the libraries\. It is categorised as a Destructive tool in the Pinako AI Bridge 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 delete_library_group? +

Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for delete_library_group: 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 Pinako AI Bridge. Nothing to install.

What risk level is delete_library_group? +

delete_library_group 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 delete_library_group? +

Yes. Add a rate_limit block to the delete_library_group 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 delete_library_group completely? +

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

delete_library_group is provided by the Pinako AI Bridge MCP server (teleomorph/pinako-mcp). 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.