change_service_for_router · CloudStack MCP Server MCP

WHAT IT DOES

What change_service_for_router does on CloudStack MCP Server

AI agents use change_service_for_router to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

WHY IT NEEDS A POLICY

Why change_service_for_router needs a policy

This tool modifies the configuration of a network router by changing its service offering (e.g., CPU, memory allocation). It is a reversible write operation since the service offering can be changed back, but it carries high severity because misconfiguring a router's service offering can disrupt network connectivity for all dependent workloads.

From the tool's definition 'Change service offering for a router' — modifies the service offering (compute resources) assigned to a router

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_service_for_router Rate-limited

change_service_for_router stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "change_service_for_router": {
      "limits": [
        {
          "counter": "change_service_for_router_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about change_service_for_router

What does the change_service_for_router tool do? +

Change service offering for a router. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on change_service_for_router? +

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

change_service_for_router is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit change_service_for_router? +

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

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

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