create_role
AI agents use create_role to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.
Creating an IAM role is a reversible write operation that establishes identity and access policies in AWS. While significant in blast radius (high severity due to potential for privilege escalation if misconfigured), it is not irreversible (roles can be deleted) and does not directly move money or execute arbitrary code.
From the tool's definition Tool name 'create_role' indicates creation of an IAM role, which is a write operation that establishes new cloud identity and permission structures. The description is empty, limiting certainty.
Attacks that exploit this kind of access
create_role. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for create_role: 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 Awslabs Valkey. Nothing to install.
create_role 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_role 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_role. 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_role is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.