Get the activity feed for a ticket in TeamDynamix
AI agents call tdx_tickets_feed_get to retrieve information from TDX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves historical activity/comments associated with a ticket. It has no side effects, does not execute commands, does not modify data, and does not involve financial transactions. It is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Get the activity feed for a ticket' — this retrieves existing ticket activity data without modifying or deleting it.
Attacks that exploit this kind of access
Get the activity feed for a ticket in TeamDynamix. It is categorised as a Read tool in the TDX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TDX MCP Server MCP server in PolicyLayer and add a rule for tdx_tickets_feed_get: 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_tickets_feed_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tdx_tickets_feed_get 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_tickets_feed_get. 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_tickets_feed_get is provided by the TDX MCP Server MCP server (uidaho-nsummers/tdx-cli-mcp). 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 →