AI agents call scout_handoff_check to retrieve information from Scout without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
scout_handoff_check merely retrieves the status of a pending handoff without modifying, executing, or deleting anything. It is a non-invasive read operation that polls for completion state. Even though it relates to a handoff mechanism (scout_handoff), checking status is inherently a Read action with minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Check[s] whether a pending handoff has been completed' and 'Returns immediately.' This is a query/polling operation with no side effects on the browser or data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Check whether a pending handoff has been completed by the human. Returns immediately. Call this every 5-10 seconds after scout_handoff until status is. It is categorised as a Read tool in the Scout MCP Server, which means it retrieves data without modifying state.
Register the Scout MCP server in PolicyLayer and add a rule for scout_handoff_check: 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 Scout. Nothing to install.
scout_handoff_check 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 scout_handoff_check 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 scout_handoff_check. 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.
scout_handoff_check is provided by the Scout MCP server (lautrek/scout). 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 →