Link an asset to a TDX ticket
AI agents use tdx-ticket-add-asset 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.
Linking an asset to a ticket creates or modifies metadata on the ticket object. While reversible (the link can be removed), it alters the ticket's state and associations. This is neither a read (no retrieval), destructive (reversible), execute (no code/command execution), nor financial. Write is the appropriate category.
From the tool's definition The tool performs 'Link an asset to a TDX ticket', which modifies ticket data by creating a relationship between a ticket and an asset. This is a write operation that changes ticket state reversibly.
Attacks that exploit this kind of access
Link an asset to a TDX ticket. 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-add-asset: 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-add-asset 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-add-asset 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-add-asset. 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-add-asset 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 →