Search for tickets in TeamDynamix. Returns abbreviated results (no Description/Attributes). Use tdx_tickets_get for full details.
AI agents call tdx_tickets_search to retrieve information from TDX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing ticket data and returns results without creating, modifying, deleting, or executing any operations. It is a standard read/search operation with no side effects. The low severity reflects minimal blast radius—an AI agent misusing this would only retrieve ticketing information it likely has authorization to access, not alter system state.
From the tool's definition Tool name is 'tdx_tickets_search' and description states it 'Search[es] for tickets' and 'Returns abbreviated results'.
Attacks that exploit this kind of access
Search for tickets in TeamDynamix. Returns abbreviated results (no Description/Attributes). Use tdx_tickets_get for full details. It is categorised as a Read tool in the TDX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TDX MCP Server MCP server in PolicyLayer and add a rule for tdx_tickets_search: 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 TDX MCP Server. Nothing to install.
tdx_tickets_search 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 tdx_tickets_search 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 tdx_tickets_search. 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.
tdx_tickets_search is provided by the TDX MCP Server MCP server (uidaho-nsummers/tdx-cli-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 →