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-skills/run-keyboard-journey.md
What run_keyboard_journey does on A11y Agent Skills
AI agents invoke run_keyboard_journey to trigger actions in A11y Agent Skills. 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.
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
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 Skills, 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 Skills, 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 Skills MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the A11y Agent Skills 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 Skills. 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 Skills MCP server (smukh/a11y-agent-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A11y Agent Skills, and thousands of servers like it.
Across the catalogue