tdx_tickets_update · TDX MCP Server MCP: Risk & Policy

WHAT IT DOES

What tdx_tickets_update does on TDX MCP Server

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

WHY IT NEEDS A POLICY

Why tdx_tickets_update needs a policy

This tool modifies existing tickets reversibly through patch operations. It is Write rather than Execute because it operates on structured data with explicit paths and values (RFC 6902 semantics), not arbitrary code execution. It is not Destructive because patch operations can be undone/reverted.

From the tool's definition 'Update an existing ticket' with JSON Patch operations including add/remove/replace operations that modify ticket state; 'path' and 'value' parameters allow targeted field modifications without deletion

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdx_tickets_update Rate-limited

tdx_tickets_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": {
    "tdx_tickets_update": {
      "limits": [
        {
          "counter": "tdx_tickets_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 TDX MCP Server, so you can run agents against it safely.

FAQ

Questions about tdx_tickets_update

What does the tdx_tickets_update tool do? +

Update an existing ticket in TeamDynamix using JSON Patch operations (RFC 6902). Each patch has op (add/remove/replace), path, and value. It is categorised as a Write tool in the TDX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tdx_tickets_update? +

Register the TDX MCP Server MCP server in PolicyLayer and add a rule for tdx_tickets_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 TDX MCP Server. Nothing to install.

What risk level is tdx_tickets_update? +

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

Can I rate-limit tdx_tickets_update? +

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

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

tdx_tickets_update is provided by the TDX MCP Server MCP server (uidaho-nsummers/tdx-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.