Partial update of a TDX ticket (only specified fields)
AI agents use tdx-ticket-patch 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.
The tool updates ticket records in a controlled manner by modifying only specified fields, which is a classic Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve data (Read).
From the tool's definition Tool name contains 'patch' and description states 'Partial update of a TDX ticket (only specified fields)' — patch operations modify data reversibly without deletion.
Attacks that exploit this kind of access
Partial update of a TDX ticket (only specified 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.
Register the TDX MCP Server MCP server in PolicyLayer and add a rule for tdx-ticket-patch: 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.
tdx-ticket-patch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tdx-ticket-patch 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.
Set action: deny in the PolicyLayer policy for tdx-ticket-patch. 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.
tdx-ticket-patch 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →