Critical Risk →

delete_custom_cloud_pricing

Delete custom cloud pricing configuration.

How to control delete_custom_cloud_pricing ↓

What delete_custom_cloud_pricing does on MCP Server for Coroot

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

Critical Risk

Why delete_custom_cloud_pricing needs a policy

This tool irreversibly deletes configuration data (custom cloud pricing). Deletion is a destructive action that cannot be undone without manual reconfiguration. While not as critical as deleting live application data, misconfiguration could impact billing accuracy and cost tracking across infrastructure.

From the tool's definition Tool name 'delete_custom_cloud_pricing' explicitly performs deletion. Description states 'Delete custom cloud pricing configuration' which is an irreversible removal of configuration data.

Documented attack patterns abuse exactly the kind of access delete_custom_cloud_pricing gives an agent:

How to control delete_custom_cloud_pricing

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Coroot, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_custom_cloud_pricing:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_custom_cloud_pricing"
  ]
}

delete_custom_cloud_pricing disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP Server for Coroot — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_custom_cloud_pricing

What does the delete_custom_cloud_pricing tool do? +

Delete custom cloud pricing configuration. It is categorised as a Destructive tool in the MCP Server for Coroot 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_custom_cloud_pricing? +

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

What risk level is delete_custom_cloud_pricing? +

delete_custom_cloud_pricing 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_custom_cloud_pricing? +

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

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

delete_custom_cloud_pricing is provided by the MCP Server for Coroot MCP server (jamesbrink/mcp-coroot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for Coroot tool call.

Start from MCP Server for Coroot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

61 MCP Server for Coroot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.