This record as markdown: /tools/aws/update-table-metadata-location.md
What update_table_metadata_location does on AWS
AI agents use update_table_metadata_location 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 update_table_metadata_location is rated Medium
The action modifies metadata about table location, which is a reversible write operation that could affect data accessibility and queries but does not delete data or execute arbitrary code. Severity is medium because misconfiguration could disrupt data access or cause queries to fail, but effects are typically recoverable by updating the location again.
From the tool's definition Tool name 'update_table_metadata_location' indicates modification of table metadata. Sibling tools include 'append_rows_to_table' and other data manipulation operations, suggesting this server manages data resources.
Attacks that exploit this kind of access
The rule that runs update_table_metadata_location 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 update_table_metadata_location, this is the rule to start with:
update_table_metadata_location 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 update_table_metadata_location call is checked against it from then on.
Questions about update_table_metadata_location
update_table_metadata_location 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 update_table_metadata_location: 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.
update_table_metadata_location 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 update_table_metadata_location 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 update_table_metadata_location. 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.
update_table_metadata_location 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