run_keyboard_journey
Run a bounded declarative keyboard journey against a public page. Arbitrary JavaScript is not accepted.
This record as markdown: /tools/a11y-agent-mcp/run-keyboard-journey.md
What run_keyboard_journey does on A11y Agent
AI agents invoke run_keyboard_journey to trigger actions in A11y Agent. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
journey | object | Yes | |
viewport | object | — | |
timeoutMs | integer | — | |
reducedMotion | boolean | — |
Parameters from the server's own tool schema.
Why run_keyboard_journey is rated High
Executes keyboard interactions on web pages; effects depend on target page state and actions specified.
From the tool's definition runs bounded declarative keyboard journey against public page
Risk signalsAccepts URL/endpoint input (url) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs run_keyboard_journey safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A11y Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_keyboard_journey, this is the rule to start with:
run_keyboard_journey stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A11y Agent, apply this rule, and every run_keyboard_journey call is checked against it from then on.
Questions about run_keyboard_journey
Run a bounded declarative keyboard journey against a public page. Arbitrary JavaScript is not accepted. It is categorised as a Execute tool in the A11y Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_keyboard_journey accepts 5 parameters: url, journey, viewport, timeoutMs, reducedMotion. Required: url, journey. The full parameter table on this page comes from the server's own tool schema.
Register the A11y Agent MCP server in PolicyLayer and add a rule for run_keyboard_journey: 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 A11y Agent. Nothing to install.
run_keyboard_journey 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 run_keyboard_journey 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 run_keyboard_journey. 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.
run_keyboard_journey is provided by the A11y Agent MCP server (@a11y-agent/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A11y Agent, and thousands of servers like it.
Across the catalogue