Update a DynamoDB table
AI agents use dynamodb_table_update to create or update resources in AWS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS MCP Server environment.
This tool modifies DynamoDB table configuration (e.g., throughput, TTL, attributes, billing mode) but does not delete the table or data irreversibly. Schema updates are reversible through subsequent updates. Severity is high because table modifications can disrupt service availability and affect billing if throughput settings are altered unexpectedly by an AI agent.
From the tool's definition Tool name 'dynamodb_table_update' and description 'Update a DynamoDB table' indicate modification of table configuration or schema, which is a reversible write operation on infrastructure.
Attacks that exploit this kind of access
Update a DynamoDB table. It is categorised as a Write tool in the AWS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for dynamodb_table_update: 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 MCP Server. Nothing to install.
dynamodb_table_update 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 dynamodb_table_update 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 dynamodb_table_update. 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.
dynamodb_table_update is provided by the AWS MCP Server MCP server (rishikavikondala/mcp-server-aws). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →