Critical Risk →

clear_console_logs

Clear captured console logs

Part of the Camoufox server.

clear_console_logs can permanently delete data in Camoufox, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CAMOUFOX →

Free to start. No card required.

AI agents may call clear_console_logs to permanently remove or destroy resources in Camoufox. 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 clear_console_logs in a loop, permanently destroying resources in Camoufox. 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_console_logs"
  ]
}

See the full Camoufox policy for all 42 tools.

Get this rule live on your own Camoufox server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CAMOUFOX →

View all 42 tools →

These attack patterns abuse exactly the kind of access clear_console_logs gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so clear_console_logs only ever does what you allow.

SECURE CAMOUFOX →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the clear_console_logs tool do? +

Clear captured console logs. It is categorised as a Destructive tool in the Camoufox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_console_logs? +

Register the Camoufox MCP server in PolicyLayer and add a rule for clear_console_logs: 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 Camoufox. Nothing to install.

What risk level is clear_console_logs? +

clear_console_logs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_console_logs? +

Yes. Add a rate_limit block to the clear_console_logs 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.

How do I block clear_console_logs completely? +

Set action: deny in the PolicyLayer policy for clear_console_logs. 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.

What MCP server provides clear_console_logs? +

clear_console_logs is provided by the Camoufox MCP server (camoufox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Camoufox tool call.

Deterministic rules across all 42 Camoufox 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.