Fill an input or textarea with new text, replacing any existing content. Use when the user wants to enter text into a form field, search box, or editable element. Prefer pilot_fill over pilot_type for inputs because it is faster and clears existing content automatically. Parameters: - ref: Elemen...
AI agents use pilot_fill to create or update resources in Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pilot environment.
pilot_fill modifies form fields and editable elements by replacing their content with new text. This is a Write operation because it creates or modifies data reversibly—the action can be undone by clearing the field or refilling it with previous content. It does not execute arbitrary code, delete data permanently, or move money.
From the tool's definition Tool description states it 'Fill an input or textarea with new text, replacing any existing content' and is used 'when the user wants to enter text into a form field, search box, or editable element.' This is a reversible modification of data/state in a web…
Documented attack patterns abuse exactly the kind of access pilot_fill 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_fill:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_fill": {
"limits": [
{
"counter": "pilot_fill_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pilot_fill stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fill an input or textarea with new text, replacing any existing content. Use when the user wants to enter text into a form field, search box, or editable element. Prefer pilot_fill over pilot_type for inputs because it is faster and clears existing content automatically. Parameters: - ref: Element reference from snapshot (e.g.,. It is categorised as a Write tool in the Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_fill: 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_fill is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pilot_fill 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_fill. 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_fill 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.