Read or write browser web storage (localStorage and sessionStorage). Use when the user wants to inspect stored application data, check feature flags, debug session state, or set a specific localStorage value. Sensitive values (tokens, secrets, API keys) are automatically redacted for security. Pa...
AI agents use pilot_storage 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.
While the tool can read storage (Read category), its primary risk is the write capability to modify localStorage and sessionStorage. An AI agent could alter application state, feature flags, session tokens, or other client-side data that affects application behavior.
From the tool's definition Tool description states "Read or write browser web storage" with parameters "set_key" and "set_value" that allow setting localStorage values. The tool explicitly supports write operations: "sets this key in localStorage to the value in set_value".
Documented attack patterns abuse exactly the kind of access pilot_storage 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_storage:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_storage": {
"limits": [
{
"counter": "pilot_storage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pilot_storage 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.
Read or write browser web storage (localStorage and sessionStorage). Use when the user wants to inspect stored application data, check feature flags, debug session state, or set a specific localStorage value. Sensitive values (tokens, secrets, API keys) are automatically redacted for security. Parameters: - set_key: If provided, sets this key in localStorage to the value in set_value - set_value: The value to set for set_key in localStorage (omit to read all storage instead) Returns: When reading: JSON object with localStorage and sessionStorage contents (sensitive values redacted as. 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_storage: 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_storage 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_storage 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_storage. 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_storage 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.