AI agents use pylon_remove_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.
Removing followers from an issue modifies the issue's follower list, but this is a reversible action (followers can be re-added). It does not delete the issue itself or any critical data, making it a Write operation rather than Destructive. Misuse could disrupt notifications for stakeholders, hence medium severity.
From the tool's definition Remove team members or customers from following a Pylon issue
Attacks that exploit this kind of access
Remove team members or customers from following 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_remove_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_remove_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_remove_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_remove_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_remove_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.
pylon_remove_issue_followers is one line of Pylon's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →