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

restart_network

Restart network with cleanup

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/restart-network.md

What restart_network does on CloudStack MCP Server

AI agents invoke restart_network 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 restart_network is rated High

This tool executes a network restart command, which is an operational action with external effects on infrastructure. It is not a simple Read operation (no data retrieval), not Write (not creating/modifying data reversibly), not Destructive (restart is typically reversible), and not Financial.

From the tool's definition Tool name 'restart_network' with description 'Restart network with cleanup' indicates execution of a network restart operation. The 'cleanup' parameter suggests side effects that alter network state.

Questions about restart_network

What does the restart_network tool do? +

Restart network with cleanup. 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 restart_network? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for restart_network: 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 restart_network? +

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

Can I rate-limit restart_network? +

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

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

restart_network 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.