AI agents use pylon_create_tag to create or update resources in Pylon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pylon environment.
Creating a tag is a reversible write operation. Tags are metadata used for organization and filtering; creating one has minimal blast radius. An AI could create spam tags or clutter the tag namespace, but this is low-impact compared to financial, destructive, or execute-level risks. Confidence is high because the description is clear and the intent unambiguous.
From the tool's definition Tool description states 'Create a new tag' — a straightforward creation operation that adds a new categorization resource without modifying or deleting existing data.
Attacks that exploit this kind of access
Create a new tag for categorizing issues and contacts. It is categorised as a Write tool in the Pylon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pylon MCP server in PolicyLayer and add a rule for pylon_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 Pylon. Nothing to install.
pylon_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 pylon_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 pylon_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.
pylon_create_tag is provided by the Pylon MCP server (@customer-support-success/pylon-mcp-server). 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 →