Clear cookies from the browser. Optionally filter by name(s) to remove specific cookies. Without a filter, clears all cookies for the current page.
Part of the Charlotte server.
Free to start. No card required.
AI agents may call charlotte_clear_cookies to permanently remove or destroy resources in Charlotte. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call charlotte_clear_cookies in a loop, permanently destroying resources in Charlotte. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"charlotte_clear_cookies"
]
}See the full Charlotte policy for all 43 tools.
These attack patterns abuse exactly the kind of access charlotte_clear_cookies gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Clear cookies from the browser. Optionally filter by name(s) to remove specific cookies. Without a filter, clears all cookies for the current page.. It is categorised as a Destructive tool in the Charlotte MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Charlotte MCP server in PolicyLayer and add a rule for charlotte_clear_cookies: 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 Charlotte. Nothing to install.
charlotte_clear_cookies 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 charlotte_clear_cookies 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 charlotte_clear_cookies. 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.
charlotte_clear_cookies is provided by the Charlotte MCP server (@ticktockbent/charlotte). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 43 Charlotte tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.