AI agents call knowledge_status 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.
The name pattern 'status' is characteristic of read-only query tools that return current state. Without a description, confidence is moderate, but given it's part of a BBS client MCP server where status queries are typical for understanding system or bot state, and no language suggests modification, deletion, or execution, Read is the most appropriate category with low severity due to information-only impact.
From the tool's definition Tool name 'knowledge_status' suggests querying or retrieving state information. The empty description prevents direct verification, but context from sibling tools (analyze_combat_readiness, assumed_bot_status, bbs_auto_learn_*) suggests this retrieves…
Attacks that exploit this kind of access
knowledge_status. 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 knowledge_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 Mcp Bbs. Nothing to install.
knowledge_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 knowledge_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 knowledge_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.
knowledge_status 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 →