AI agents call ticket_get to retrieve information from Trac without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing ticket information without creating, modifying, or deleting data. It is a read-only query operation that returns ticket metadata and content. The mention of 'raw=true' parameter for format control does not change the fundamental read-only nature of the operation. No side effects or data mutations occur.
From the tool's definition Tool name 'ticket_get' and description 'Get full ticket details including summary, description, status, and owner' indicates a retrieval operation with no modification.
Attacks that exploit this kind of access
Get full ticket details including summary, description, status, and owner. Use ticket_changelog for history. Set raw=true to get description in original TracWiki format without conversion. It is categorised as a Read tool in the Trac MCP Server, which means it retrieves data without modifying state.
Register the Trac MCP server in PolicyLayer and add a rule for ticket_get: 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 Trac. Nothing to install.
ticket_get 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_get 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_get. 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_get is provided by the Trac MCP server (nerpatech/trac-mcp-server). 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 →