AI agents call pylon_search_issues to retrieve information from Pylon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves/queries data (issues) based on filter criteria and returns results. It has no side effects and does not modify, delete, execute code, or commit financial obligations. This is a standard Read operation. The presence of sibling tools like pylon_create_issue, pylon_delete_issue, and pylon_add_tags confirms this is distinct from write/destructive operations.
From the tool's definition Tool description explicitly states 'Search issues using structured filters' — a read-only query operation with no mention of modification, deletion, or execution of external effects.
Attacks that exploit this kind of access
Search issues using structured filters; requires at least one filter. For unfiltered listing, use pylon_get_issues instead. It is categorised as a Read tool in the Pylon MCP Server, which means it retrieves data without modifying state.
Register the Pylon MCP server in PolicyLayer and add a rule for pylon_search_issues: 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_search_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pylon_search_issues 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_search_issues. 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_search_issues 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 →