tm_verify_domain_http · Tm MCP: Risk & Policy

WHAT IT DOES

What tm_verify_domain_http does on Tm

AI agents invoke tm_verify_domain_http to trigger actions in Tm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why tm_verify_domain_http needs a policy

The name implies executing an HTTP verification request against a domain, which is an external operation with side effects (verifying domain ownership/reachability). Since the description is empty, confidence is reduced.

From the tool's definition Tool name 'tm_verify_domain_http' suggests triggering an HTTP-based domain verification action; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tm_verify_domain_http Rate-limited

tm_verify_domain_http stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tm_verify_domain_http": {
      "limits": [
        {
          "counter": "tm_verify_domain_http_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about tm_verify_domain_http

What does the tm_verify_domain_http tool do? +

tm_verify_domain_http. It is categorised as a Execute tool in the Tm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tm_verify_domain_http? +

Register the Tm MCP server in PolicyLayer and add a rule for tm_verify_domain_http: 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.

What risk level is tm_verify_domain_http? +

tm_verify_domain_http is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tm_verify_domain_http? +

Yes. Add a rate_limit block to the tm_verify_domain_http 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 tm_verify_domain_http completely? +

Set action: deny in the PolicyLayer policy for tm_verify_domain_http. 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 tm_verify_domain_http? +

tm_verify_domain_http 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.