Get details of a specific ticket.
AI agents call get_ticket_tool to retrieve information from MCP Request-tracker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns ticket details without creating, modifying, deleting, or executing any external operations. It is a straightforward read operation with minimal risk if misused by an AI agent—worst case being unauthorized information disclosure of ticket contents.
From the tool's definition Tool name 'get_ticket_tool' and description 'Get details of a specific ticket' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific ticket. It is categorised as a Read tool in the MCP Request-tracker MCP Server, which means it retrieves data without modifying state.
Register the MCP Request-tracker MCP server in PolicyLayer and add a rule for get_ticket_tool: 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 MCP Request-tracker. Nothing to install.
get_ticket_tool 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 get_ticket_tool 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 get_ticket_tool. 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.
get_ticket_tool is provided by the MCP Request-tracker MCP server (crunchtools/mcp-request-tracker). 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 →