Get all ticket field definitions (standard + custom fields). Returns field metadata including name, type, label, options (for select fields), and custom flag. Use to discover instance-specific ticket schema.
AI agents call ticket_fields 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 queries and retrieves metadata about ticket field schemas. It performs a read-only discovery operation that returns structural information about the Trac instance without creating, modifying, deleting, or executing any actions. The severity is low because misuse would only expose schema information, not compromise data integrity or trigger unwanted operations.
From the tool's definition Tool description states 'Get all ticket field definitions' and 'Returns field metadata' — purely retrieval operations with no modification, deletion, or execution capability. No side effects mentioned.
Attacks that exploit this kind of access
Get all ticket field definitions (standard + custom fields). Returns field metadata including name, type, label, options (for select fields), and custom flag. Use to discover instance-specific ticket schema. 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_fields: 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_fields 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_fields 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_fields. 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_fields 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 →