AI agents use localstorage_set to create or update resources in MCP Camoufox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Camoufox environment.
This tool creates or modifies localStorage key-value pairs, which are reversible changes to client-side storage. Within the context of a stealth browser automation server designed to bypass detection systems, setting localStorage items could be used to manipulate session state, inject malicious tokens, or modify application behavior in ways that affect subsequent interactions.
From the tool's definition localstorage_set sets (modifies/creates) localStorage items. The description explicitly states 'Set a localStorage item,' which is a write operation that modifies client-side persistent data.
Documented attack patterns abuse exactly the kind of access localstorage_set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for localstorage_set:
{
"version": "1",
"default": "deny",
"tools": {
"localstorage_set": {
"limits": [
{
"counter": "localstorage_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}localstorage_set 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.
Set a localStorage item. It is categorised as a Write tool in the MCP Camoufox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for localstorage_set: 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 MCP Camoufox. Nothing to install.
localstorage_set 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 localstorage_set 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 localstorage_set. 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.
localstorage_set is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Camoufox, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
102 MCP Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.