stop_partition · zRobot WSAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_partition does on zRobot WSAPI MCP Server

AI agents invoke stop_partition to trigger actions in zRobot WSAPI 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 IT NEEDS A POLICY

Why stop_partition needs a policy

This tool executes a command that halts a running partition, which is an irreversible operational action affecting system availability. While not permanently destructive to data, stopping a partition is an Execute-class action because it runs a command with external side effects. Severity is high because misuse could interrupt production workloads on mainframe systems.

From the tool's definition stop_partition stops a partition on IBM Z Hardware Management Console systems. This triggers an external operation (partition shutdown) whose effects depend on which partition argument is provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_partition Rate-limited

stop_partition stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_partition": {
      "limits": [
        {
          "counter": "stop_partition_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about stop_partition

What does the stop_partition tool do? +

Stop a partition. It is categorised as a Execute tool in the zRobot WSAPI 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 stop_partition? +

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

What risk level is stop_partition? +

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

Can I rate-limit stop_partition? +

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

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

stop_partition is provided by the zRobot WSAPI MCP Server MCP server (thirrukumar/zrobot-wsapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.