AI agents call pylon_find_similar_issues_for_account 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 retrieves and queries existing issues without creating, modifying, or deleting any data. It has no side effects beyond returning search results. The blast radius of misuse is minimal — an agent could retrieve information about issues but cannot alter system state. This is a straightforward Read operation.
From the tool's definition Tool description states 'Find issues from the same company/account' — a query/search operation with no modification of data. The verb 'find' indicates retrieval only.
Attacks that exploit this kind of access
Find issues from the same company/account to identify company-wide problems. 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_account: 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_account 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_account 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_account. 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_account 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 →