staticx_connect_custom_domain · StaticX MCP Server MCP

WHAT IT DOES

What staticx_connect_custom_domain does on StaticX MCP Server

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

WHY IT NEEDS A POLICY

Why staticx_connect_custom_domain needs a policy

This tool modifies project DNS configuration by connecting a custom domain—a reversible write action that creates or updates records rather than executing arbitrary code or permanently destroying data. The severity is medium because misconfiguration could redirect traffic unintentionally, affecting site availability and user experience, but the action itself is reversible.

From the tool's definition "Move a project to a custom domain" indicates modification of domain configuration and routing, which is a reversible write operation. The tool creates or updates DNS configuration state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

staticx_connect_custom_domain Rate-limited

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

FAQ

Questions about staticx_connect_custom_domain

What does the staticx_connect_custom_domain tool do? +

Move a project to a custom domain and return the one DNS record the user must create. It is categorised as a Write tool in the StaticX 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 staticx_connect_custom_domain? +

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

What risk level is staticx_connect_custom_domain? +

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

Can I rate-limit staticx_connect_custom_domain? +

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

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

staticx_connect_custom_domain is provided by the StaticX MCP Server MCP server (madprodworks-coder/staticx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.