Check whether a target URL or hostname is allowed by the local bug bounty scope configuration.
AI agents call tool_check_scope to retrieve information from ScopePilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup or validation against a local configuration to determine scope membership. It is a read-only query operation that informs authorization decisions but does not itself execute tests, modify data, or change system state. The low severity reflects minimal blast radius—misuse results only in incorrect scope determinations that may guide (but do not force) subsequent actions by other tools.
From the tool's definition Tool description states it 'Check[s] whether a target URL or hostname is allowed by the local bug bounty scope configuration.' The verb is 'check' which is a query/verification operation with no side effects.
Attacks that exploit this kind of access
Check whether a target URL or hostname is allowed by the local bug bounty scope configuration. It is categorised as a Read tool in the ScopePilot MCP MCP Server, which means it retrieves data without modifying state.
Register the ScopePilot MCP server in PolicyLayer and add a rule for tool_check_scope: 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 ScopePilot MCP. Nothing to install.
tool_check_scope 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 tool_check_scope 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 tool_check_scope. 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.
tool_check_scope is provided by the ScopePilot MCP server (rens1215/scopepilot-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 →