AI agents call ticket_list to retrieve information from Tpm 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 project ticket metadata without side effects. It enables listing/searching tickets but cannot create, modify, delete, or execute operations. The minimal data exposure (IDs and basic status fields) and read-only nature classify it as a Read operation with low risk.
From the tool's definition Tool explicitly 'List[s] ticket IDs with status/priority' and returns only 'id, status, priority' - a read-only query with no data modification. Description confirms use of separate 'ticket_get for details', indicating this is a retrieval function.
Attacks that exploit this kind of access
PROJECT MANAGEMENT: List ticket IDs with status/priority. Returns id, status, priority only - use ticket_get for details. It is categorised as a Read tool in the Tpm MCP Server, which means it retrieves data without modifying state.
Register the Tpm MCP server in PolicyLayer and add a rule for ticket_list: 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 Tpm. Nothing to install.
ticket_list 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 ticket_list 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 ticket_list. 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.
ticket_list is provided by the Tpm MCP server (urjitbhatia/tpm-mcp). 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 →