Updates a library group\
AI agents use set_library_group_description 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.
This tool creates or modifies data reversibly by updating metadata (a description) associated with a library group. The action is non-destructive and can be undone by updating the description again. It falls clearly into the Write category. Severity is low because modifying a group description has minimal blast radius — it affects only organizational metadata with no side effects on other systems or data integrity.
From the tool's definition Tool name contains 'set' and description states 'Updates a library group' — indicates modification of existing data (group description) without deletion or destructive action.
Attacks that exploit this kind of access
Updates a library group\. 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.
Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for set_library_group_description: 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.
set_library_group_description is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_library_group_description 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 set_library_group_description. 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.
set_library_group_description 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.
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 →