Check if the Pilot Chrome extension is connected and routing commands through the user
AI agents call pilot_extension_status 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 performs a simple state check—querying whether the Pilot Chrome extension is currently connected. It retrieves information about the extension's status and routing state without side effects, data modification, code execution, or financial impact. This is a read-only diagnostic operation with minimal blast radius if misused.
From the tool's definition Tool name 'pilot_extension_status' and description 'Check if the Pilot Chrome extension is connected' indicate a status query operation that retrieves the connection state of an extension without modifying any data or triggering external actions.
Documented attack patterns abuse exactly the kind of access pilot_extension_status 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_extension_status:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_extension_status": {}
}
}pilot_extension_status 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.
Check if the Pilot Chrome extension is connected and routing commands through the user. 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_extension_status: 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_extension_status 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_extension_status 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_extension_status. 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_extension_status 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.