Get custom attribute definitions for a TDX component (e.g. tickets, assets, CIs). Returns attribute IDs, names, types, and choices needed for creating/updating items with custom attributes.
AI agents call tdx-attributes-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 schema/metadata information about custom attributes in TDX (their IDs, names, types, and available choices). It has no side effects and does not modify, delete, or execute anything. It is a pure read/query operation that returns reference data needed for other operations. The blast radius of misuse is minimal—an AI agent could only learn what attributes exist, which is low-impact information.
From the tool's definition Tool name contains 'get' and description states 'Get custom attribute definitions' and 'Returns attribute IDs, names, types, and choices'. No create, update, delete, or execute operations are mentioned. The tool retrieves metadata about attribute definitions.
Attacks that exploit this kind of access
Get custom attribute definitions for a TDX component (e.g. tickets, assets, CIs). Returns attribute IDs, names, types, and choices needed for creating/updating items with custom attributes. 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-attributes-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-attributes-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-attributes-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-attributes-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-attributes-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 →