update_table_metadata_location

THE RISK

Medium Risk

Why update_table_metadata_location needs a policy

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.

Documented attack patterns abuse exactly the kind of access update_table_metadata_location gives an agent:

POLICY

How to control update_table_metadata_location

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 update_table_metadata_location:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_table_metadata_location": {
      "limits": [
        {
          "counter": "update_table_metadata_location_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register AWS — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Args: key: The key to delete Returns: Destructive cache_delete_many Delete multiple values from the cache. Args: keys: List of keys to delete Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Args: keys: Li Destructive delete Delete a Valkey key. Args: key (str): The key to delete. Returns: Destructive delete_access_key delete_access_key Destructive delete_datastore Delete a data store from AWS HealthImaging. Destructive delete_group delete_group

All 300 AWS tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

Govern customer-ops agents → PII redaction, approval on external messages, and no-bulk-delete rules on the records agents change.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about update_table_metadata_location

What does the update_table_metadata_location tool do? +

update_table_metadata_location. 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.

How do I enforce a policy on update_table_metadata_location? +

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.

What risk level is update_table_metadata_location? +

update_table_metadata_location is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_table_metadata_location? +

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.

How do I block update_table_metadata_location completely? +

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.

What MCP server provides update_table_metadata_location? +

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.

Enforce policy on every AWS tool call.

Start from AWS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →