Get the feed/comments for a TDX ticket
AI agents call tdx-ticket-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 retrieves existing ticket feed/comments data from the TeamDynamix system. It performs a query operation with no capability to create, modify, delete, or execute external actions. The blast radius of misuse is minimal—an attacker could view ticket comments they may not be authorized to see, but this is a read-only disclosure risk, not a write, execute, or destructive risk.
From the tool's definition Tool name 'tdx-ticket-feed-get' uses the verb 'get'; description states 'Get the feed/comments for a TDX ticket', which retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get the feed/comments for a TDX ticket. 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-ticket-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-ticket-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-ticket-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-ticket-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-ticket-feed-get 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 →