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

confirm_dangerous_action

Confirm a dangerous action that requires explicit user approval

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/confirm-dangerous-action.md

What confirm_dangerous_action does on CloudStack MCP Server

AI agents invoke confirm_dangerous_action to trigger actions in CloudStack MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why confirm_dangerous_action is rated High

This tool is a confirmation gate for dangerous actions in a CloudStack environment managing 735+ API methods. Confirming a dangerous action causes the underlying destructive, financial, or high-impact operation to execute. The blast radius is critical because it could unleash any category of irreversible infrastructure change — VM deletion, network teardown, storage purge, etc.

From the tool's definition 'Confirm a dangerous action that requires explicit user approval' - this tool explicitly gates destructive/dangerous operations and its execution triggers those operations to proceed

Questions about confirm_dangerous_action

What does the confirm_dangerous_action tool do? +

Confirm a dangerous action that requires explicit user approval. It is categorised as a Execute tool in the CloudStack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on confirm_dangerous_action? +

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

What risk level is confirm_dangerous_action? +

confirm_dangerous_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit confirm_dangerous_action? +

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

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

confirm_dangerous_action is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on CloudStack 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 CloudStack 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.