List open support tickets. Optionally filter by customer id.
AI agents call list_open_tickets to retrieve information from Acme Operations Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays support ticket data without creating, modifying, deleting, executing code, or committing financial actions. It is a straightforward read operation that allows filtering but performs no side effects. Low severity because exposure of open tickets could leak customer information but doesn't enable direct operational harm.
From the tool's definition Tool name 'list_open_tickets' and description 'List open support tickets. Optionally filter by customer id.' indicate a query/retrieval operation with no modification.
Attacks that exploit this kind of access
List open support tickets. Optionally filter by customer id. It is categorised as a Read tool in the Acme Operations Assistant MCP Server, which means it retrieves data without modifying state.
Register the Acme Operations Assistant MCP server in PolicyLayer and add a rule for list_open_tickets: 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 Acme Operations Assistant. Nothing to install.
list_open_tickets 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 list_open_tickets 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 list_open_tickets. 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.
list_open_tickets is provided by the Acme Operations Assistant MCP server (yesidevelop/simple-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 →