Update an existing support issue/ticket. Use this to change status (e.g., mark as resolved), reassign to different team members, update priority, or modify details as you work on the issue.
Part of the Pylon Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use pylon_update_issue to create or modify resources in Pylon Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call pylon_update_issue repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Pylon Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
pylon_update_issue:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Pylon Server policy for all 29 tools.
Agents calling write-class tools like pylon_update_issue have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Update an existing support issue/ticket. Use this to change status (e.g., mark as resolved), reassign to different team members, update priority, or modify details as you work on the issue.. It is categorised as a Write tool in the Pylon Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for pylon_update_issue. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pylon Server MCP server.
pylon_update_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_update_issue rule in your Intercept 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 Intercept policy for pylon_update_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_update_issue is provided by the Pylon Server MCP server (marcinwyszynski/pylon-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept