add_inline_policy
AI agents use add_inline_policy to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.
The 'add_' prefix indicates a write operation that creates or modifies data. Adding an inline policy is a reversible configuration change (policies can be removed or updated), not an irreversible deletion. However, the blast radius is high because an AI agent could grant unintended permissions or escalate privileges.
From the tool's definition Tool named 'add_inline_policy' with empty description. Based on naming convention, this tool adds/creates an IAM inline policy, which modifies AWS IAM configuration.
Attacks that exploit this kind of access
add_inline_policy. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for add_inline_policy: 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 Awslabs Valkey. Nothing to install.
add_inline_policy 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 add_inline_policy 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 add_inline_policy. 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.
add_inline_policy is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.