add_custom_domain · PlugLayer MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_custom_domain does on PlugLayer MCP Server

AI agents use add_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 add_custom_domain needs a policy

This tool creates or modifies configuration by adding a custom domain to a project/deployment. While domain additions can have downstream effects (DNS resolution, SSL certificate provisioning), the operation itself is reversible and does not delete data or trigger financial transactions. It fits the Write category (creates/modifies data reversibly).

From the tool's definition The tool 'add_custom_domain' creates/adds a new domain association to an infrastructure resource. The description states 'Add a custom domain', which is a reversible modification operation (the domain can subsequently be removed or replaced via the sibling…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_custom_domain Rate-limited

add_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": {
    "add_custom_domain": {
      "limits": [
        {
          "counter": "add_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 add_custom_domain

What does the add_custom_domain tool do? +

Add a custom domain. Confirm whether the user wants this custom domain or the default pluglayer.io subdomain first. After the provider is known, use provider_name to tailor the DNS instructions. 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 add_custom_domain? +

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

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

Can I rate-limit add_custom_domain? +

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

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

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