AI agents use rename_table 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.
Renaming a table modifies its metadata and affects dependent queries/applications without deleting data. This is Write rather than Destructive because the operation is reversible (can rename back). Severity is high because unauthorized renames can break application logic, disrupt reporting, or cause confusion in multi-tenant systems.
From the tool's definition Tool name 'rename_table' indicates modification of data structures. No description provided, but the sibling tools include data and policy manipulation (add_user_to_group, attach_group_policy, append_rows_to_table), suggesting this server manages AWS…
Documented attack patterns abuse exactly the kind of access rename_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_table:
{
"version": "1",
"default": "deny",
"tools": {
"rename_table": {
"limits": [
{
"counter": "rename_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_table 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.
Free to start. No card required.
rename_table. 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_table: 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_table 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_table 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_table. 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_table 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.
Start from AWS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.