attach_custom_domain · PlugLayer MCP Server MCP

WHAT IT DOES

What attach_custom_domain does on PlugLayer MCP Server

AI agents use attach_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 attach_custom_domain needs a policy

This tool modifies app infrastructure by attaching a domain and optionally changing the primary domain, which are configuration changes that can be reversed (domains can be detached or the primary can be reassigned). This is a Write operation: creates or modifies data reversibly. It is not Destructive because the operation does not irreversibly delete data and can be undone.

From the tool's definition Tool description states 'Attach a verified custom domain to an app' and 'Set make_primary=true if you want it to become the app's main URL' — these are reversible modifications to app configuration (attach/detach are reciprocal operations).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

attach_custom_domain Rate-limited

attach_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": {
    "attach_custom_domain": {
      "limits": [
        {
          "counter": "attach_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 attach_custom_domain

What does the attach_custom_domain tool do? +

Attach a verified custom domain to an app. Set make_primary=true if you want it to become the app's main URL. 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 attach_custom_domain? +

Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for attach_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 attach_custom_domain? +

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

Can I rate-limit attach_custom_domain? +

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

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

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