ticket_update · Tpm MCP: Risk & Policy

WHAT IT DOES

What ticket_update does on Tpm

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

WHY IT NEEDS A POLICY

Why ticket_update needs a policy

The 'ticket_update' tool modifies existing project/task data in a SQLite database but does not delete or destroy records (which would be Destructive), nor execute arbitrary code (Execute). It enables editing of ticket fields, making it a Write operation.

From the tool's definition Tool name 'ticket_update' indicates modification of existing ticket/task data. Description is empty, but context from sibling tools (task_create, note_add, org_create, project_create) shows this server manages a local SQLite project tracking system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticket_update Rate-limited

ticket_update 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": {
    "ticket_update": {
      "limits": [
        {
          "counter": "ticket_update_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 Tpm, so you can run agents against it safely.

FAQ

Questions about ticket_update

What does the ticket_update tool do? +

ticket_update. It is categorised as a Write tool in the Tpm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ticket_update? +

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

What risk level is ticket_update? +

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

Can I rate-limit ticket_update? +

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

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

ticket_update is provided by the Tpm MCP server (urjitbhatia/tpm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.