create_domain_name · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What create_domain_name does on AWS IoT SiteWise MCP Server

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

WHY IT NEEDS A POLICY

Why create_domain_name needs a policy

The tool creates a new domain name, which is a reversible write operation on AWS IoT SiteWise resources. This modifies infrastructure state but does not delete data irreversibly or execute arbitrary code. However, confidence is moderate (0.72) because the description is empty, leaving some ambiguity about the exact scope and whether it might have side effects like triggering deployments or affecting live systems.

From the tool's definition Tool name 'create_domain_name' indicates creation of a new domain name resource; sibling tools like 'add_inline_policy', 'add_user_to_group', and other 'add'/'create' operations confirm this server performs write operations on AWS infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_domain_name Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_domain_name": {
      "limits": [
        {
          "counter": "create_domain_name_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 AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

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 AWS IoT SiteWise 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 AWS IoT SiteWise 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 AWS IoT SiteWise 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.