Medium Risk

create_domain_name

create_domain_name

How to control create_domain_name ↓

What create_domain_name does on Amazon ECS MCP Server

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

Medium Risk

Why create_domain_name needs a policy

The tool name suggests creation of a domain name resource, which is a Write operation (reversible modification). Without a description, confidence is moderate. Severity is medium because domain misconfiguration could disrupt services, but domain creation itself is typically not immediately destructive or financial.

From the tool's definition Tool name 'create_domain_name' indicates creation of a new resource. No description provided to refine classification. In AWS ECS context, creating a domain name likely registers or provisions DNS/networking resources.

Documented attack patterns abuse exactly the kind of access create_domain_name gives an agent:

How to control create_domain_name

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_domain_name:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_domain_name": {
      "limits": [
        {
          "counter": "create_domain_name_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Amazon ECS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_domain_name

What does the create_domain_name tool do? +

create_domain_name. It is categorised as a Write tool in the Amazon ECS 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 create_domain_name? +

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

What risk level is create_domain_name? +

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

Can I rate-limit create_domain_name? +

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

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

create_domain_name is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon ECS MCP Server tool call.

Start from Amazon ECS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.