Get multi-instance coordination pool status and recent activity.
AI agents call pool_status to retrieve information from MidOS - MCP Community Library without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves operational status and activity logs from a coordination pool. It has no side effects, does not modify data, execute code, delete resources, or commit financial actions. It is a straightforward read/query operation with minimal security risk even if called by an untrusted agent.
From the tool's definition Tool name is 'pool_status' and description states it 'Get[s] multi-instance coordination pool status and recent activity' — purely retrieves status information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get multi-instance coordination pool status and recent activity. It is categorised as a Read tool in the MidOS - MCP Community Library MCP Server, which means it retrieves data without modifying state.
Register the MidOS - MCP Community Library MCP server in PolicyLayer and add a rule for pool_status: 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 MidOS - MCP Community Library. Nothing to install.
pool_status 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 pool_status 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 pool_status. 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.
pool_status is provided by the MidOS - MCP Community Library MCP server (midos-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 →