AI agents invoke scout_press_key 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.
Pressing keyboard keys triggers browser actions whose effects depend entirely on the current context and arguments — pressing Enter could submit forms, confirm dialogs, or trigger navigation; Escape could cancel operations. This constitutes executing external browser operations with variable and potentially significant side effects, placing it in the Execute category.
From the tool's definition Press a keyboard key (e.g. Enter, Escape, ArrowDown, Backspace)
Attacks that exploit this kind of access
Press a keyboard key (e.g. Enter, Escape, ArrowDown, Backspace). 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_press_key: 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_press_key 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_press_key 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_press_key. 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_press_key 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 →