get_ticket_correspondence
AI agents call get_ticket_correspondence to retrieve information from RT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves correspondence data from Request Tracker tickets. The server is documented as read-only and the tool's name indicates a GET operation that fetches existing ticket correspondence without modifying, deleting, or executing operations. The empty description is compensated by the clear read-only server context and the straightforward semantic meaning of 'get_ticket_correspondence'.
From the tool's definition Tool name 'get_ticket_correspondence' combined with server description stating 'Read-only MCP server' and listing 'correspondence viewing' as a core capability. Server explicitly designed for retrieval operations with no modification capability.
Attacks that exploit this kind of access
get_ticket_correspondence. It is categorised as a Read tool in the RT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RT MCP Server MCP server in PolicyLayer and add a rule for get_ticket_correspondence: 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 RT MCP Server. Nothing to install.
get_ticket_correspondence 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_correspondence 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_correspondence. 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_correspondence is provided by the RT MCP Server MCP server (msekoranja/rt-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 →