delete_provider

Delete a workspace provider by slug. This is irreversible and will break prompts, configs, and virtual keys that reference it; use delete_integration for the org source instead. Returns success after the provider is removed.

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/codeswhat-portkey-admin-mcp/delete-provider.md

What delete_provider does on Portkey Admin

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

Why delete_provider is rated Critical

This tool permanently removes data (a workspace provider) with explicit irreversibility noted in the description. The cascading impact on dependent entities (prompts, configs, virtual keys) and the impossibility of undo make it Destructive rather than Write. Destructive is the most severe applicable category and takes precedence.

From the tool's definition Tool description explicitly states 'Delete a workspace provider by slug. This is irreversible and will break prompts, configs, and virtual keys that reference it'.

Questions about delete_provider

What does the delete_provider tool do? +

Delete a workspace provider by slug. This is irreversible and will break prompts, configs, and virtual keys that reference it; use delete_integration for the org source instead. Returns success after the provider is removed. It is categorised as a Destructive tool in the Portkey Admin 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 delete_provider? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for delete_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 Portkey Admin. Nothing to install.

What risk level is delete_provider? +

delete_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 delete_provider? +

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

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

delete_provider is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Portkey Admin, 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 Portkey Admin'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.