AI agents call oboe_session_status to retrieve information from Obo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns summary statistics—a read-only query operation with no side effects. It fits the Read category (queries data, no side effects). The blast radius is minimal since an AI misuse would only expose session metadata, not cause data loss or financial impact.
From the tool's definition Tool name 'oboe_session_status' and description 'Return summary statistics for an OBO session' indicate a retrieval operation that queries and returns data about an existing session without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Return summary statistics for an OBO session. It is categorised as a Read tool in the Obo MCP Server, which means it retrieves data without modifying state.
Register the Obo MCP server in PolicyLayer and add a rule for oboe_session_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 Obo. Nothing to install.
oboe_session_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 oboe_session_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 oboe_session_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.
oboe_session_status is provided by the Obo MCP server (warnes-innovations/oboe-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 →