tdx-ticket-update · TDX MCP Server MCP: Risk & Policy

WHAT IT DOES

What tdx-ticket-update does on TDX MCP Server

AI agents use tdx-ticket-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-ticket-update needs a policy

This tool modifies ticket records by replacing their field contents. While not destructive (data is not deleted), it is a reversible write operation that changes existing IT service management records. Severity is high because bulk field replacement on tickets could affect service continuity, audit trails, and business processes if misused by an AI agent (e.g., updating all tickets to wrong status or priority).

From the tool's definition Tool description states 'Full update of a TDX ticket (replaces all fields)', indicating it modifies and overwrites ticket data. The 'update' verb combined with 'replaces all fields' confirms write-level data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdx-ticket-update Rate-limited

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

FAQ

Questions about tdx-ticket-update

What does the tdx-ticket-update tool do? +

Full update of a TDX ticket (replaces all fields). 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-ticket-update? +

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

What risk level is tdx-ticket-update? +

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

Can I rate-limit tdx-ticket-update? +

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

Set action: deny in the PolicyLayer policy for tdx-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 tdx-ticket-update? +

tdx-ticket-update is provided by the TDX MCP Server MCP server (umzcio/teamdynamix-mcp-connector). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.