AI agents call bbs_get_screen_saver_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.
This tool retrieves/queries the status of a screen saver (saved count and directory location) without side effects. It is a read-only operation that returns data about an existing resource. No data is created, modified, deleted, or executed. Severity is low because the information exposed (screen saver status) presents minimal security risk even if accessed by an untrusted agent.
From the tool's definition Tool name 'bbs_get_screen_saver_status' and description 'Get screen saver status including saved count and directory' indicate a query operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Get screen saver status including saved count and directory. 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 bbs_get_screen_saver_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.
bbs_get_screen_saver_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 bbs_get_screen_saver_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 bbs_get_screen_saver_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.
bbs_get_screen_saver_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 →