remove_library_from_group · Pinako AI Bridge MCP

WHAT IT DOES

What remove_library_from_group does on Pinako AI Bridge

AI agents use remove_library_from_group to create or update resources in Pinako AI Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pinako AI Bridge environment.

WHY IT NEEDS A POLICY

Why remove_library_from_group needs a policy

This tool modifies the organizational relationship between a library and a group by unlinking them, but it does not delete any data — the library is explicitly preserved. This is a reversible structural change (the library can be re-added to the group), making it a Write operation. Misuse could cause organizational disruption but no data loss.

From the tool's definition Removes a library from a group, returning it to the standalone library card list right after the group. The library itself is preserved.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_library_from_group Rate-limited

remove_library_from_group stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_library_from_group": {
      "limits": [
        {
          "counter": "remove_library_from_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pinako AI Bridge, so you can run agents against it safely.

FAQ

Questions about remove_library_from_group

What does the remove_library_from_group tool do? +

Removes a library from a group, returning it to the standalone library card list right after the group. The library itself is preserved. No-op if the library wasn\. It is categorised as a Write tool in the Pinako AI Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_library_from_group? +

Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for remove_library_from_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 remove_library_from_group? +

remove_library_from_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_library_from_group? +

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

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

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