AI agents use create_tag to create or update resources in Peecai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Peecai environment.
This tool creates a new tag, which is a write operation that modifies project data. Tags are typically low-impact metadata that can be deleted or modified later (as evidenced by the sibling 'delete_tag' tool), making this a Write rather than Destructive action. Severity is low because tag creation has minimal blast radius—it only adds organizational metadata without affecting core data or operations.
From the tool's definition Tool name 'create_tag' and description 'Create a new tag within a Peec AI project' indicate data creation with reversible effects.
Attacks that exploit this kind of access
Create a new tag within a Peec AI project. It is categorised as a Write tool in the Peecai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Peecai MCP server in PolicyLayer and add a rule for 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 Peecai. Nothing to install.
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 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 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.
create_tag is provided by the Peecai MCP server (mcp-server-peecai). 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 →