Extract all form elements on the page as structured JSON with their types, names, IDs, and current values. Use when the user wants to understand form structure, see all input fields with their current values, check form methods and actions, or plan form filling automation. Password field values a...
AI agents call pilot_page_forms to retrieve information from Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns structured data about form elements present on the current page. It has no side effects — it does not modify, submit, or interact with any forms. It is a pure data extraction/query operation. Severity is low since it only reads page structure, though it could expose sensitive field values (passwords are redacted).
From the tool's definition Extract all form elements on the page as structured JSON with their types, names, IDs, and current values. Password field values are redacted for security.
Documented attack patterns abuse exactly the kind of access pilot_page_forms 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_page_forms:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_page_forms": {}
}
}pilot_page_forms is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Extract all form elements on the page as structured JSON with their types, names, IDs, and current values. Use when the user wants to understand form structure, see all input fields with their current values, check form methods and actions, or plan form filling automation. Password field values are redacted for security. Parameters: (none) Returns: JSON array of form objects, each containing the form. It is categorised as a Read tool in the Pilot MCP Server, which means it retrieves data without modifying state.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_page_forms: 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_page_forms is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pilot_page_forms 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_page_forms. 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_page_forms 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.