identity_put_resource_policy · Awslabs Valkey MCP

WHAT IT DOES

What identity_put_resource_policy does on Awslabs Valkey

AI agents use identity_put_resource_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.

WHY IT NEEDS A POLICY

Why identity_put_resource_policy needs a policy

The tool name implies putting/writing an identity-based or resource-based policy, which would create or update policy documents. This is reversible (policies can be updated again) but has significant security implications as it controls access to resources. However, the empty description creates some ambiguity—it could potentially have destructive aspects if it overwrites without warning.

From the tool's definition Tool name 'identity_put_resource_policy' indicates a resource policy modification operation. The 'put' verb suggests creating or overwriting a policy, which is a Write operation that modifies access control configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

identity_put_resource_policy Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about identity_put_resource_policy

What does the identity_put_resource_policy tool do? +

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

How do I enforce a policy on identity_put_resource_policy? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for identity_put_resource_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.

What risk level is identity_put_resource_policy? +

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

Can I rate-limit identity_put_resource_policy? +

Yes. Add a rate_limit block to the identity_put_resource_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.

How do I block identity_put_resource_policy completely? +

Set action: deny in the PolicyLayer policy for identity_put_resource_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.

What MCP server provides identity_put_resource_policy? +

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