AI agents call oboe_list_sessions 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.
List operations query and return existing data without modifying, creating, or deleting anything. No side effects or state changes occur. This is a standard read-only retrieval of session metadata/references, making it a Read-category tool with low blast radius.
From the tool's definition Tool name 'oboe_list_sessions' is a list operation that retrieves session data. The description is empty, but based on naming convention and sibling tools (oboe_get_session, oboe_list_items) which are clearly retrieval operations, this follows the same…
Attacks that exploit this kind of access
oboe_list_sessions. 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_list_sessions: 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_list_sessions 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_list_sessions 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_list_sessions. 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_list_sessions 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 →