update_partition · zRobot WSAPI MCP Server MCP

WHAT IT DOES

What update_partition does on zRobot WSAPI MCP Server

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

WHY IT NEEDS A POLICY

Why update_partition needs a policy

The tool modifies partition configuration properties but does not delete or destroy resources (which would be Destructive), nor does it execute arbitrary commands or trigger state changes like start/stop (which would be Execute). Update operations are reversible Write actions.

From the tool's definition Tool name 'update_partition' and description 'Update partition properties' indicate data modification. Context shows this is part of IBM Z Hardware Management Console integration managing HMC systems and partitions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_partition Rate-limited

update_partition 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": {
    "update_partition": {
      "limits": [
        {
          "counter": "update_partition_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 zRobot WSAPI MCP Server, so you can run agents against it safely.

FAQ

Questions about update_partition

What does the update_partition tool do? +

Update partition properties. It is categorised as a Write tool in the zRobot WSAPI 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 update_partition? +

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

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

Can I rate-limit update_partition? +

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

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

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

// THE FULL RECORD

update_partition is one line of zRobot WSAPI MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →