AI agents use bbs_set_screen_saving to create or update resources in Mcp Bbs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Bbs environment.
This tool creates or modifies system configuration (screen saving state) which is reversible—disabling what was enabled or vice versa. It does not execute arbitrary code, delete data, or cause financial impact. The severity is medium because saving screens could capture sensitive session data from a BBS system, and an agent could inadvertently enable/disable this feature in ways that affect logging and audit trails.
From the tool's definition Tool enables/disables saving screens to disk, which modifies the configuration state of screen capture behavior. The description states it can 'Enable or disable' a feature, indicating it creates or modifies settings.
Attacks that exploit this kind of access
Enable or disable saving screens to disk. It is categorised as a Write tool in the Mcp Bbs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Bbs MCP server in PolicyLayer and add a rule for bbs_set_screen_saving: 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_set_screen_saving is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bbs_set_screen_saving 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_set_screen_saving. 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_set_screen_saving 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 →