Inverse direction of add_to_library: clones tree or library nodes INTO the browser\
AI agents use add_to_bookmarks 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 adds bookmark entries to the browser, which is a data modification operation. While bookmarks can be deleted or modified later (reversible), the action itself creates new data structures. There is no indication of irreversible deletion (Destructive), code execution (Execute), financial impact (Financial), or data retrieval only (Read).
From the tool's definition Tool description states it 'clones tree or library nodes INTO the browser' - this modifies bookmark state by adding/creating new bookmark entries, which is a reversible write operation.
Attacks that exploit this kind of access
Inverse direction of add_to_library: clones tree or library nodes INTO the browser\. 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 add_to_bookmarks: 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.
add_to_bookmarks 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 add_to_bookmarks 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 add_to_bookmarks. 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.
add_to_bookmarks 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 →