detach_custom_domain · PlugLayer MCP Server MCP

WHAT IT DOES

What detach_custom_domain does on PlugLayer MCP Server

AI agents use detach_custom_domain to create or update resources in PlugLayer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PlugLayer MCP Server environment.

WHY IT NEEDS A POLICY

Why detach_custom_domain needs a policy

Detaching a custom domain modifies the association between a domain and an app (reversible — the domain can be re-attached), and explicitly preserves the verification record. This is a configuration change (Write), not a permanent deletion. Misuse could cause downtime for the associated domain, hence medium severity.

From the tool's definition Detach a custom domain from its app while keeping verification

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

detach_custom_domain Rate-limited

detach_custom_domain 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": {
    "detach_custom_domain": {
      "limits": [
        {
          "counter": "detach_custom_domain_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 PlugLayer MCP Server, so you can run agents against it safely.

FAQ

Questions about detach_custom_domain

What does the detach_custom_domain tool do? +

Detach a custom domain from its app while keeping verification. It is categorised as a Write tool in the PlugLayer 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 detach_custom_domain? +

Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for detach_custom_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 PlugLayer MCP Server. Nothing to install.

What risk level is detach_custom_domain? +

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

Can I rate-limit detach_custom_domain? +

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

How do I block detach_custom_domain completely? +

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

What MCP server provides detach_custom_domain? +

detach_custom_domain is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.