Put an item into a DynamoDB table
AI agents use dynamodb_item_put 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 creates or modifies data reversibly in DynamoDB. While it can overwrite existing items, it does not irreversibly delete data (making it Write rather than Destructive). The severity is high because misconfigured or malicious use could corrupt application data, but the blast radius is limited to individual items unless chained with other operations.
From the tool's definition Tool name 'dynamodb_item_put' and description 'Put an item into a DynamoDB table' indicate creation or modification of data in DynamoDB. The 'put' operation creates a new item or overwrites an existing one.
Attacks that exploit this kind of access
Put an item into 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_item_put: 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_item_put 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_item_put 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_item_put. 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_item_put 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 →