This record as markdown: /tools/aws/create-access-key.md
What create_access_key does on AWS
AI agents use create_access_key to create or update resources in AWS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS environment.
Why create_access_key is rated Medium
Access key creation is a reversible Write operation that adds new authentication credentials to an AWS account. While not destructive, it has high severity due to blast radius: misconfigured or malicious use could grant unauthorized API access. Confidence lowered from 0.9 to 0.85 due to empty description; 'create_' prefix and AWS context strongly indicate credential generation.
From the tool's definition Tool named 'create_access_key' on AWS server; sibling tools include user/group/policy management operations indicating IAM context. Creating access keys generates new credentials that modify AWS account state.
Attacks that exploit this kind of access
The rule that runs create_access_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_access_key, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every create_access_key call is checked against it from then on.
Questions about create_access_key
create_access_key is a write tool on the AWS MCP server. It is categorised as a Write tool in the AWS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS 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. Nothing to install.
create_access_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_access_key is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue