cdp_deactivate_provision_instance

Deactivate a provisioned instance (DELETE /provisions/instances/{id}).

SERVERCDP MCP Server SOURCEatharva-joshi77/cdp-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/atharva-joshi77-cdp-mcp/cdp-deactivate-provision-instance.md

What cdp_deactivate_provision_instance does on CDP MCP Server

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

Why cdp_deactivate_provision_instance is rated Critical

The tool performs an irreversible deactivation of a provisioned instance via a DELETE endpoint. This is a destructive operation that cannot be undone without manual intervention (re-provisioning). The blast radius is significant as it affects infrastructure/instance availability.

From the tool's definition 'Deactivate a provisioned instance (DELETE /provisions/instances/{id})' - uses HTTP DELETE method and deactivates/removes a provisioned instance, an irreversible action.

Questions about cdp_deactivate_provision_instance

What does the cdp_deactivate_provision_instance tool do? +

Deactivate a provisioned instance (DELETE /provisions/instances/{id}). It is categorised as a Destructive tool in the CDP MCP Server 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 cdp_deactivate_provision_instance? +

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

What risk level is cdp_deactivate_provision_instance? +

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

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

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

cdp_deactivate_provision_instance is provided by the CDP MCP Server MCP server (atharva-joshi77/cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on CDP MCP Server, 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 CDP MCP Server'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.