Delete a partition
AI agents call delete_partition to permanently remove resources in zRobot WSAPI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a partition, which cannot be undone and affects critical IBM Z hardware infrastructure. Deletion is the hallmark of the Destructive category and ranks highest in severity due to the potential for infrastructure outage, data loss, and inability to recover the deleted partition without external recovery procedures.
From the tool's definition Tool name 'delete_partition' and description 'Delete a partition' directly indicate irreversible deletion of a partition resource on IBM Z Hardware Management Console systems.
Attacks that exploit this kind of access
Delete a partition. It is categorised as a Destructive tool in the zRobot WSAPI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the zRobot WSAPI MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_partition is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →