AI agents use pylon_add_issue_followers 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.
Adding followers to an issue is a write operation that creates relationships or modifies issue state. While reversible (followers can be removed), it alters data structure. The severity is medium because the blast radius is limited to issue notification/visibility changes rather than destructive data loss or financial impact.
From the tool's definition Tool description states it 'Add[s] team members (user_ids) or customers (contact_ids) as followers to a Pylon issue' — this modifies issue metadata by adding followers, a reversible change to an existing resource.
Attacks that exploit this kind of access
Add team members (user_ids) or customers (contact_ids) as followers to a Pylon issue. 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_add_issue_followers: 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_add_issue_followers 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_add_issue_followers 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_add_issue_followers. 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_add_issue_followers 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 →