identity_create_oauth2_provider · Awslabs Valkey MCP

WHAT IT DOES

What identity_create_oauth2_provider does on Awslabs Valkey

AI agents use identity_create_oauth2_provider 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_create_oauth2_provider needs a policy

Creating an OAuth2 provider modifies security infrastructure and can enable authentication flows. This is a reversible write operation (the provider can be deleted), but affects identity and access control systems. Severity is high because misconfiguration could grant unintended access or enable credential hijacking, though the operation itself is reversible. Confidence is reduced due to empty tool description.

From the tool's definition Tool name 'identity_create_oauth2_provider' with 'create' action prefix indicates creation of a new OAuth2 provider resource. Empty description limits certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

identity_create_oauth2_provider Rate-limited

identity_create_oauth2_provider 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_create_oauth2_provider": {
      "limits": [
        {
          "counter": "identity_create_oauth2_provider_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_create_oauth2_provider

What does the identity_create_oauth2_provider tool do? +

identity_create_oauth2_provider. 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_create_oauth2_provider? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for identity_create_oauth2_provider: 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_create_oauth2_provider? +

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

Can I rate-limit identity_create_oauth2_provider? +

Yes. Add a rate_limit block to the identity_create_oauth2_provider 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_create_oauth2_provider completely? +

Set action: deny in the PolicyLayer policy for identity_create_oauth2_provider. 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_create_oauth2_provider? +

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