Get all HTML attributes of a specific element as a JSON object. Use when the user wants to inspect an element
AI agents call pilot_page_attrs 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.
The tool performs inspection/querying of element attributes, which is a read-only operation with no side effects. It does not create, modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal—an attacker could only exfiltrate visible HTML attributes from the current page state.
From the tool's definition Tool description states 'Get all HTML attributes of a specific element as a JSON object' and 'Use when the user wants to inspect an element'. This is a retrieval operation that reads DOM properties without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access pilot_page_attrs 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_attrs:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_page_attrs": {}
}
}pilot_page_attrs 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.
Get all HTML attributes of a specific element as a JSON object. Use when the user wants to inspect an element. 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_attrs: 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_attrs 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_attrs 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_attrs. 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_attrs 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.