APPENDS tags to a node, deduping and preserving order of existing tags. Use this when the user says
AI agents use add_tags 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 appending tags to nodes. It does not retrieve data (Read), execute arbitrary operations (Execute), permanently delete data (Destructive), or involve financial transactions (Financial). The modification is reversible—tags can be removed or edited later.
From the tool's definition APPENDS tags to a node, deduping and preserving order of existing tags. The tool modifies existing data (tags) in a reversible manner without deletion or destruction.
Attacks that exploit this kind of access
APPENDS tags to a node, deduping and preserving order of existing tags. Use this when the user says. 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_tags: 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_tags 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_tags 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_tags. 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_tags 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 →