Partial update of a TDX asset
AI agents use tdx-asset-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.
This tool modifies asset records in TeamDynamix, but does so reversibly (updates can be undone or corrected). It is not Destructive because patching is not deletion or irreversible overwriting. It is not Execute because it does not run arbitrary code or trigger external operations with argument-dependent side effects. It falls squarely into Write: creates or modifies data reversibly.
From the tool's definition Tool name 'tdx-asset-patch' and description 'Partial update of a TDX asset' indicate a reversible modification operation. PATCH is an HTTP verb used for partial updates that do not destroy data.
Attacks that exploit this kind of access
Partial update of a TDX asset. 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-asset-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-asset-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-asset-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-asset-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-asset-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 →