Get detailed information about a specific partition
AI agents call get_partition to retrieve information from zRobot WSAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves partition details, which is a read-only query operation. It does not create, modify, delete, or execute code. The blast radius is minimal—querying partition information poses low risk even if misused by an AI agent, as it cannot alter system state or perform destructive operations. Low severity is appropriate for informational access.
From the tool's definition Tool name 'get_partition' and description 'Get detailed information about a specific partition' indicate retrieval of partition metadata without modification. Verb 'Get' is consistent with query operations; no side effects implied.
Attacks that exploit this kind of access
Get detailed information about a specific partition. It is categorised as a Read tool in the zRobot WSAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the zRobot WSAPI MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_partition is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →