AI agents use pylon_snooze_issue 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.
This is a Write operation because it modifies data (issue visibility state) in a reversible way. It does not read-only (no data retrieval), does not execute arbitrary code (no Execute), is not destructive (fully reversible and temporary), and does not involve financial transactions.
From the tool's definition Tool description states 'Temporarily hide an issue' which modifies the state/visibility of an existing issue in a reversible manner.
Attacks that exploit this kind of access
Temporarily hide an issue until a future date/time for deferred follow-up. 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_snooze_issue: 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_snooze_issue 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_snooze_issue 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_snooze_issue. 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_snooze_issue 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 →