Medium Risk

open_ticket

Open a ticket and set it active

Changes ticket workflow state

Part of the MCP Request-tracker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use open_ticket to create or modify resources in MCP Request-tracker. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call open_ticket repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach MCP Request-tracker.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

mcp-request-tracker.yaml
tools:
  open_ticket:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full MCP Request-tracker policy for all 17 tools.

Tool Name open_ticket
Category Write
Risk Level Medium

View all 17 tools →

Agents calling write-class tools like open_ticket have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the open_ticket tool do? +

Open a ticket and set it active. It is categorised as a Write tool in the MCP Request-tracker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on open_ticket? +

Add a rule in your Intercept YAML policy under the tools section for open_ticket. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MCP Request-tracker MCP server.

What risk level is open_ticket? +

open_ticket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit open_ticket? +

Yes. Add a rate_limit block to the open_ticket rule in your Intercept 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 open_ticket completely? +

Set action: deny in the Intercept policy for open_ticket. 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 open_ticket? +

open_ticket is provided by the MCP Request-tracker MCP server (mcp-request-tracker-crunchtools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on MCP Request-tracker

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.