Add a comment/feed entry to a TDX ticket
AI agents use tdx-ticket-feed-add 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.
Adding a comment to a ticket creates new data and modifies the ticket's state reversibly—the comment can be deleted or edited later. This is a Write operation (not Execute, as it doesn't run arbitrary code or shell commands; not Destructive, as it doesn't irreversibly delete data; not Read, as it modifies state).
From the tool's definition Tool name 'tdx-ticket-feed-add' and description 'Add a comment/feed entry to a TDX ticket' indicate creation of a new comment/feed entry, which is a write operation that modifies ticket data by appending to its feed/comment history.
Attacks that exploit this kind of access
Add a comment/feed entry 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-feed-add: 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-feed-add 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-feed-add 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-feed-add. 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-feed-add 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 →