This record as markdown: /tools/aws/rename.md
What rename does on AWS
AI agents use rename 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 rename is rated Medium
Renaming is a reversible modification operation that changes resource metadata without destroying data. Without a description, confidence is moderate, but AWS rename operations typically affect naming/tagging rather than core data deletion. Classified as Write rather than Destructive because the action is reversible.
From the tool's definition Tool name 'rename' suggests modifying metadata (resource name). No description provided; inferred from AWS context and sibling tools which include write operations like 'append_rows_to_table' and policy attachment.
Attacks that exploit this kind of access
The rule that runs rename 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 rename, this is the rule to start with:
rename 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 rename call is checked against it from then on.
Questions about rename
rename 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 rename: 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.
rename 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 rename 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 rename. 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.
rename 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