ticket_actions

Get valid workflow actions for a ticket

Server Trac nerpatech/trac-mcp-server
Category Read
Risk class Low
Parameters 00 required

What ticket_actions does on Trac

AI agents call ticket_actions 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.

Why ticket_actions needs a policy

This tool queries and returns information about available workflow actions for a ticket without modifying state, executing those actions, or triggering any side effects. It is a read-only operation that retrieves metadata about valid transitions/actions, making it a Read category risk with low severity.

From the tool's definition Tool description states 'Get valid workflow actions for a ticket' - a retrieval operation with no modification or execution of actions, only querying what actions are available.

Questions about ticket_actions

What does the ticket_actions tool do? +

Get valid workflow actions for a ticket. It is categorised as a Read tool in the Trac MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ticket_actions? +

Register the Trac MCP server in PolicyLayer and add a rule for ticket_actions: 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.

What risk level is ticket_actions? +

ticket_actions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ticket_actions? +

Yes. Add a rate_limit block to the ticket_actions 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.

How do I block ticket_actions completely? +

Set action: deny in the PolicyLayer policy for ticket_actions. 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.

What MCP server provides ticket_actions? +

ticket_actions 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.