ticket_create · Tpm MCP: Risk & Policy

WHAT IT DOES

What ticket_create does on Tpm

AI agents use ticket_create 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_create needs a policy

This tool creates new ticket records in the local SQLite database. While the description is empty, the naming convention and server context (project management with task tracking) clearly indicate it adds new data reversibly. It is Write rather than Execute because it modifies data through a structured API rather than running arbitrary code.

From the tool's definition Tool name 'ticket_create' indicates creation of new tickets/tasks in a project management system. Server uses SQLite for local data storage. Sibling tools include 'task_create', 'project_create', and 'note_add', which are all Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticket_create Rate-limited

ticket_create 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_create": {
      "limits": [
        {
          "counter": "ticket_create_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_create

What does the ticket_create tool do? +

ticket_create. 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_create? +

Register the Tpm MCP server in PolicyLayer and add a rule for ticket_create: 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_create? +

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

Can I rate-limit ticket_create? +

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

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

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