AI agents invoke scout_drag to trigger actions in Scout. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Dragging elements in a browser can trigger writes, moves, or state changes (e.g., reordering items, moving files, triggering drop events) whose effects depend on the context. This is a browser action that executes an interaction, making Execute the appropriate category. Severity is medium because the blast radius depends on what is being dragged and where.
From the tool's definition 'Drag one element onto another' — triggers a browser interaction (drag-and-drop) that manipulates UI elements and can cause side effects depending on the target application.
Attacks that exploit this kind of access
Drag one element onto another. It is categorised as a Execute tool in the Scout MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Scout MCP server in PolicyLayer and add a rule for scout_drag: 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_drag is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scout_drag 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_drag. 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_drag 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 →