create_access_key · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What create_access_key does on AWS IoT SiteWise MCP Server

AI agents use create_access_key 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_access_key needs a policy

Creating access keys is a write operation that generates new authentication credentials, modifying AWS IAM state. While reversible (keys can be deleted), misuse could grant unauthorized programmatic access to AWS resources. Severity is high due to the blast radius of compromised credentials, though not critical since key rotation/deletion are available and financial impact depends on downstream resource access.

From the tool's definition Tool name 'create_access_key' indicates creation of AWS access credentials. Sibling tools include 'add_inline_policy' and 'add_user_to_group', suggesting identity and access management operations. Tool description is empty, limiting direct evidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_access_key Rate-limited

create_access_key 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_access_key": {
      "limits": [
        {
          "counter": "create_access_key_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_access_key

What does the create_access_key tool do? +

create_access_key. 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_access_key? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for create_access_key: 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_access_key? +

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

Can I rate-limit create_access_key? +

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

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

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