Update the TTL settings for a table
AI agents use dynamodb_update_ttl 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 metadata (TTL configuration) but does not delete data or cause irreversible loss. The change is reversible—TTL can be disabled or reconfigured. It is categorized as Write rather than Execute because it configures a service setting rather than triggering code execution.
From the tool's definition Tool name 'dynamodb_update_ttl' and description 'Update the TTL settings for a table' indicate modification of table configuration. TTL (Time-To-Live) is a reversible configuration setting that controls automatic item expiration behavior.
Attacks that exploit this kind of access
Update the TTL settings for a 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_update_ttl: 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_update_ttl 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_update_ttl 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_update_ttl. 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_update_ttl 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 →