AI agents call support_list_tickets to retrieve information from AgentOS 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 support ticket data for display purposes only. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial operations. It is a straightforward Read operation with minimal risk even if misused by an AI agent, as listing existing tickets cannot cause harm.
From the tool's definition Tool name 'support_list_tickets' and description 'List all support tickets for a user' indicate a retrieval operation with no data modification or external effects.
Attacks that exploit this kind of access
List all support tickets for a user. It is categorised as a Read tool in the AgentOS MCP Server, which means it retrieves data without modifying state.
Register the AgentOS MCP server in PolicyLayer and add a rule for support_list_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 AgentOS. Nothing to install.
support_list_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 support_list_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 support_list_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.
support_list_tickets is provided by the AgentOS MCP server (netflypsb/agentos). 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 →