tm_delete_domain
AI agents call tm_delete_domain to permanently remove resources in Tm — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Domain deletion is irreversible and removes configuration or verification records. While severity is not critical (unlikely to affect production systems directly), it qualifies as Destructive rather than Write because deletion cannot be undone. The high severity reflects potential workflow disruption if domains are incorrectly removed during load-test management.
From the tool's definition Tool name 'tm_delete_domain' contains 'delete', indicating irreversible removal of data. The empty description limits certainty, but context from the server (domain verification in load-testing and CI-failure triage) and sibling destructive tools…
Attacks that exploit this kind of access
tm_delete_domain. It is categorised as a Destructive tool in the Tm MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tm MCP server in PolicyLayer and add a rule for tm_delete_domain: 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 Tm. Nothing to install.
tm_delete_domain is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tm_delete_domain 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 tm_delete_domain. 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.
tm_delete_domain is provided by the Tm MCP server (trafficmorph-gif/tm-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 →