Get information about dependency management in bbot scans
AI agents call get_dependency_info 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 is a read-only operation that queries dependency information. It has no side effects on the system or scan state. The verb 'Get information' clearly indicates a retrieval action. Given the context of a security scanning tool, accessing dependency metadata poses minimal risk—it cannot trigger scans, modify configurations, or delete data.
From the tool's definition Tool name is 'get_dependency_info' and description states it retrieves information ('Get information') about dependency management in BBOT scans. No modification, deletion, or execution of scans occurs.
Attacks that exploit this kind of access
Get information about dependency management in bbot scans. 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 get_dependency_info: 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.
get_dependency_info 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_dependency_info 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_dependency_info. 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_dependency_info 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 →