tdx-cmdb-update · TDX MCP Server MCP: Risk & Policy

WHAT IT DOES

What tdx-cmdb-update does on TDX MCP Server

AI agents use tdx-cmdb-update 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.

WHY IT NEEDS A POLICY

Why tdx-cmdb-update needs a policy

This is a Write operation because it modifies CMDB configuration items, allowing an AI agent to alter critical infrastructure metadata. While reversible (not Destructive), a full update of configuration items is high-severity due to potential for misconfiguring business-critical IT assets, dependencies, and relationships in the CMDB that downstream systems and workflows depend on.

From the tool's definition "Full update of a TDX configuration item" — this tool modifies existing CMDB records. The verb "update" and context of configuration management indicate reversible write operations that change stored configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdx-cmdb-update Rate-limited

tdx-cmdb-update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tdx-cmdb-update": {
      "limits": [
        {
          "counter": "tdx-cmdb-update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TDX MCP Server, so you can run agents against it safely.

FAQ

Questions about tdx-cmdb-update

What does the tdx-cmdb-update tool do? +

Full update of a TDX configuration item. 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.

How do I enforce a policy on tdx-cmdb-update? +

Register the TDX MCP Server MCP server in PolicyLayer and add a rule for tdx-cmdb-update: 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.

What risk level is tdx-cmdb-update? +

tdx-cmdb-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tdx-cmdb-update? +

Yes. Add a rate_limit block to the tdx-cmdb-update 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.

How do I block tdx-cmdb-update completely? +

Set action: deny in the PolicyLayer policy for tdx-cmdb-update. 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.

What MCP server provides tdx-cmdb-update? +

tdx-cmdb-update 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.