List all available bbot presets
AI agents call list_bbot_presets to retrieve information from BBOT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval (listing) with no side effects, no code execution, and no data modification. It falls squarely within the Read category. Severity is low because listing presets poses minimal risk—the worst outcome is information disclosure of available preset names, which is typically non-sensitive configuration metadata.
From the tool's definition Tool name 'list_bbot_presets' and description 'List all available bbot presets' indicate a read-only operation that retrieves and enumerates preset configurations without modifying or executing any scans.
Attacks that exploit this kind of access
List all available bbot presets. It is categorised as a Read tool in the BBOT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BBOT MCP Server MCP server in PolicyLayer and add a rule for list_bbot_presets: 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 BBOT MCP Server. Nothing to install.
list_bbot_presets 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 list_bbot_presets 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 list_bbot_presets. 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.
list_bbot_presets is provided by the BBOT MCP Server MCP server (marlinkcyber/bbot-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 →