Get detailed status of a specific pool.
AI agents call get_pool_status to retrieve information from Session Buddy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves and returns status information about a pool. It does not create, modify, delete, execute code, or move money. The verb 'Get' combined with the informational nature of 'status' confirms this is a simple data retrieval with no side effects.
From the tool's definition Tool name 'get_pool_status' and description 'Get detailed status of a specific pool' indicate a retrieval operation that queries state information without modification or side effects.
Attacks that exploit this kind of access
Get detailed status of a specific pool. It is categorised as a Read tool in the Session Buddy MCP Server, which means it retrieves data without modifying state.
Register the Session Buddy MCP server in PolicyLayer and add a rule for get_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 Session Buddy. Nothing to install.
get_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 get_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 get_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.
get_pool_status is provided by the Session Buddy MCP server (lesleslie/session-buddy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_pool_status is one line of Session Buddy'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 →