Clear cookies, localStorage, and sessionStorage.
AI agents call Clear-Browser-Data to permanently remove resources in MCP GitHub Login Automation Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes browser state data including cookies, localStorage, and sessionStorage. In the context of a GitHub login automation server, clearing this data would destroy authentication sessions, stored credentials, and other persistent browser state that cannot be recovered. This is a destructive operation with no undo capability.
From the tool's definition Clear cookies, localStorage, and sessionStorage
Attacks that exploit this kind of access
Clear cookies, localStorage, and sessionStorage. It is categorised as a Destructive tool in the MCP GitHub Login Automation Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP GitHub Login Automation Server MCP server in PolicyLayer and add a rule for Clear-Browser-Data: 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 GitHub Login Automation Server. Nothing to install.
Clear-Browser-Data is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the Clear-Browser-Data 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 Clear-Browser-Data. 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.
Clear-Browser-Data is provided by the MCP GitHub Login Automation Server MCP server (nikhil-kandekar/mcp-server-demo). 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 →