New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

foundry_deleteProviderKey

Delete a tenant provider key (DELETE /v1/foundry/provider-keys/{provider_id})

SERVERGenesis SOURCE@onesi/genesis-mcp
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/foundry-deleteproviderkey.md

What foundry_deleteProviderKey does on Genesis

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

ParameterTypeRequiredDescription
provider_id string Yes

Parameters from the server's own tool schema.

Why foundry_deleteProviderKey is rated Critical

An AI agent that decides to call foundry_deleteProviderKey doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Genesis is gone. There is no undo for destructive operations.

Questions about foundry_deleteProviderKey

What does the foundry_deleteProviderKey tool do? +

Delete a tenant provider key (DELETE /v1/foundry/provider-keys/{provider_id}). It is categorised as a Destructive tool in the Genesis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does foundry_deleteProviderKey accept? +

foundry_deleteProviderKey accepts 1 parameter: provider_id. Required: provider_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on foundry_deleteProviderKey? +

Register the Genesis MCP server in PolicyLayer and add a rule for foundry_deleteProviderKey: 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 Genesis. Nothing to install.

What risk level is foundry_deleteProviderKey? +

foundry_deleteProviderKey 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 foundry_deleteProviderKey? +

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

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

foundry_deleteProviderKey is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Genesis, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Genesis's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.