Type text character-by-character into the currently focused element, simulating real keyboard input. Use when the user wants to type into a contenteditable div, rich text editor, or a field that reacts to individual keystrokes (e.g., autocomplete, keypress events). For standard <input>/<textarea>...
AI agents invoke pilot_type to trigger actions in Pilot. 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.
This tool simulates real keyboard input into browser elements and can trigger event handlers, form submissions, and other dynamic behaviors. The 'submit' parameter can trigger form submissions or searches. In a browser automation context, typing into fields (login forms, search bars, command inputs, etc.) and submitting can trigger significant external operations.
From the tool's definition Type text character-by-character into the currently focused element, simulating real keyboard input... reacts to individual keystrokes (e.g., autocomplete, keypress events)... submit: Set to true to press Enter after typing (useful for search fields and forms)
Documented attack patterns abuse exactly the kind of access pilot_type gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_type:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_type": {
"limits": [
{
"counter": "pilot_type_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pilot_type 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.
Free to start. No card required.
Type text character-by-character into the currently focused element, simulating real keyboard input. Use when the user wants to type into a contenteditable div, rich text editor, or a field that reacts to individual keystrokes (e.g., autocomplete, keypress events). For standard <input>/<textarea> elements, prefer pilot_fill which is faster. Parameters: - text: The text string to type - submit: Set to true to press Enter after typing (useful for search fields and forms) Returns: Character count typed and whether Enter was pressed. Errors: -. It is categorised as a Execute tool in the Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_type: 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 Pilot. Nothing to install.
pilot_type 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 pilot_type 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 pilot_type. 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.
pilot_type is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.