AI agents call pylon_find_similar_issues_for_requestor 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.
This tool queries existing issue data based on requestor matching to identify patterns. It performs no creation, modification, deletion, or execution of external operations. The operation is purely informational and read-only, with no side effects or ability to change system state. Severity is low as the blast radius of misuse would be limited to data disclosure of existing issues.
From the tool's definition Tool description states it 'Find[s] issues from the same requestor' - a query/search operation that retrieves data without modifying state. The verb 'find' and the operation of identifying patterns indicates data retrieval only.
Attacks that exploit this kind of access
Find issues from the same requestor as the source issue to identify recurring patterns. 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_find_similar_issues_for_requestor: 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_find_similar_issues_for_requestor 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_find_similar_issues_for_requestor 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_find_similar_issues_for_requestor. 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_find_similar_issues_for_requestor 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 →