set_ticket_status_tool · MCP Request-tracker MCP

WHAT IT DOES

What set_ticket_status_tool does on MCP Request-tracker

AI agents use set_ticket_status_tool to create or update resources in MCP Request-tracker — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Request-tracker environment.

WHY IT NEEDS A POLICY

Why set_ticket_status_tool needs a policy

This tool modifies ticket metadata (status field) in a request-tracker system. While it changes data, status updates are typically reversible operations—a ticket's status can be changed back if needed. This qualifies as Write rather than Destructive.

From the tool's definition Tool name 'set_ticket_status_tool' and description 'Set the status of a ticket' indicate modification of ticket state. Status changes are reversible (can be changed back to previous state).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_ticket_status_tool Rate-limited

set_ticket_status_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_ticket_status_tool": {
      "limits": [
        {
          "counter": "set_ticket_status_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Request-tracker, so you can run agents against it safely.

FAQ

Questions about set_ticket_status_tool

What does the set_ticket_status_tool tool do? +

Set the status of a ticket. 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 set_ticket_status_tool? +

Register the MCP Request-tracker MCP server in PolicyLayer and add a rule for set_ticket_status_tool: 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 MCP Request-tracker. Nothing to install.

What risk level is set_ticket_status_tool? +

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

Can I rate-limit set_ticket_status_tool? +

Yes. Add a rate_limit block to the set_ticket_status_tool 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 set_ticket_status_tool completely? +

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

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