Update the metadata location for an S3 table. Updates the metadata location for an S3 table. The metadata location of an S3 table must be an S3 URI that begins with the S3 table's warehouse location. The metadata location for an Apache Iceberg S3 table must end with .metadata.json, or if the met...
Part of the AWS S3 Tables MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use update_table_metadata_location to create or modify resources in AWS S3 Tables MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_table_metadata_location repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS S3 Tables MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
update_table_metadata_location:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS S3 Tables MCP Server policy for all 16 tools.
Agents calling write-class tools like update_table_metadata_location have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Update the metadata location for an S3 table. Updates the metadata location for an S3 table. The metadata location of an S3 table must be an S3 URI that begins with the S3 table's warehouse location. The metadata location for an Apache Iceberg S3 table must end with .metadata.json, or if the metadata file is Gzip-compressed, .metadata.json.gz. Permissions: You must have the s3tables:UpdateTableMetadataLocation permission to use this operation.. It is categorised as a Write tool in the AWS S3 Tables MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for update_table_metadata_location. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS S3 Tables MCP Server MCP server.
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 Intercept 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 Intercept 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 S3 Tables MCP Server MCP server (awslabs.s3-tables-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.