AI agents call get_bot_session_data to retrieve information from Mcp Bbs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing session data about a bot's identity and lifecycle state. The verb 'fetch' and lack of any write/delete/execute operations indicate a read-only query operation. The blast radius is low—obtaining session metadata poses minimal risk compared to tools that modify state or trigger actions. No side effects are described or implied.
From the tool's definition Tool name 'get_bot_session_data' and description 'Fetch persisted identity/session lifecycle for one bot' use retrieval language ('Fetch') with no indication of modification, deletion, or external effects.
Attacks that exploit this kind of access
Fetch persisted identity/session lifecycle for one bot. It is categorised as a Read tool in the Mcp Bbs MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bbs MCP server in PolicyLayer and add a rule for get_bot_session_data: 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 Mcp Bbs. Nothing to install.
get_bot_session_data 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_bot_session_data 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_bot_session_data. 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_bot_session_data is provided by the Mcp Bbs MCP server (livingstaccato/mcp-bbs). 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 →