manages browser local storage
AI agents use manage_local_storage to create or update resources in Selenium MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Selenium MCP Server environment.
Local storage management allows modification of data that persists across browser sessions, which could affect application state, user preferences, or cached credentials. However, it does not involve financial transactions, code execution on the system, or irreversible deletion of data outside the browser's control.
From the tool's definition Tool name 'manage_local_storage' and description 'manages browser local storage' indicate the tool can create, modify, or delete data stored in the browser's local storage.
Attacks that exploit this kind of access
manages browser local storage. It is categorised as a Write tool in the Selenium MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Selenium MCP Server MCP server in PolicyLayer and add a rule for manage_local_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 Selenium MCP Server. Nothing to install.
manage_local_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 manage_local_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 manage_local_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.
manage_local_storage is provided by the Selenium MCP Server MCP server (jyothishkumarav/selenium-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →