Create a new partition on a CPC
AI agents use create_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.
Creating a partition on enterprise IBM Z systems is a reversible but significant infrastructure modification that allocates computing resources and changes system configuration. This is a Write operation rather than Read (no query-only nature), Execute (not running arbitrary code), Destructive (partition can be deleted), or Financial (no money movement).
From the tool's definition Tool name 'create_partition' and description 'Create a new partition on a CPC' indicate resource creation on IBM Z Hardware Management Console systems. This modifies infrastructure state by adding a new logical partition to a Central Processor Complex.
Attacks that exploit this kind of access
Create a new partition on a CPC. 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.
Register the zRobot WSAPI MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_partition is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →