identity_delete_oauth2_provider

identity_delete_oauth2_provider

Server Awslabs Valkey awslabs.valkey-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What identity_delete_oauth2_provider does on Awslabs Valkey

AI agents call identity_delete_oauth2_provider to permanently remove resources in Awslabs Valkey — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why identity_delete_oauth2_provider needs a policy

Deletion of authentication/OAuth2 provider configurations is irreversible and would prevent users from authenticating through that provider. This has significant blast radius if triggered inappropriately by an AI agent, potentially locking users out of systems. The 'delete' verb places this in Destructive category (more severe than Execute).

From the tool's definition Tool name contains 'delete' which indicates irreversible removal of data (an OAuth2 provider configuration). Despite empty description, the semantic meaning of 'delete_oauth2_provider' clearly signals deletion operation.

Questions about identity_delete_oauth2_provider

What does the identity_delete_oauth2_provider tool do? +

identity_delete_oauth2_provider. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on identity_delete_oauth2_provider? +

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

identity_delete_oauth2_provider is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit identity_delete_oauth2_provider? +

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

Set action: deny in the PolicyLayer policy for identity_delete_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_delete_oauth2_provider? +

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.