start_partition · zRobot WSAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_partition does on zRobot WSAPI MCP Server

AI agents invoke start_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 start_partition needs a policy

This tool triggers execution of a system operation (partition startup) on IBM Z hardware infrastructure. While not destructive or financial, it is an Execute category tool because it performs an irreversible operational state change through an external system.

From the tool's definition Tool name 'start_partition' and description 'Start a partition' indicate triggering of an external operation on IBM Z Hardware.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_partition Rate-limited

start_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": {
    "start_partition": {
      "limits": [
        {
          "counter": "start_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 start_partition

What does the start_partition tool do? +

Start 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 start_partition? +

Register the zRobot WSAPI MCP Server MCP server in PolicyLayer and add a rule for start_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 start_partition? +

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

Can I rate-limit start_partition? +

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

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

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