AI agents use kinbox_create_tag to create or update resources in Kinbox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kinbox environment.
This tool creates a new tag in the Kinbox system, which is a reversible write operation. Tags are metadata/labels used for organization and categorization. While creation is non-destructive and can be reversed (via deletion), the blast radius is medium because mass or inappropriate tag creation could disrupt customer management workflows, though the impact is localized to organizational metadata rather than core…
From the tool's definition Tool name 'kinbox_create_tag' and description 'Cria uma nova tag no Kinbox' (Creates a new tag in Kinbox) indicate creation of a new data entity.
Attacks that exploit this kind of access
Cria uma nova tag no Kinbox. It is categorised as a Write tool in the Kinbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kinbox MCP server in PolicyLayer and add a rule for kinbox_create_tag: 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 Kinbox. Nothing to install.
kinbox_create_tag 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 kinbox_create_tag 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 kinbox_create_tag. 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.
kinbox_create_tag is provided by the Kinbox MCP server (vergamini65-boop/kinbox-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 →