Critical Risk →

clear_scan

Clear current scan results and reset scan state.

How to control clear_scan ↓

AI agents call clear_scan to permanently remove resources in Frida Game Hacking MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly clears/deletes accumulated scan results and resets the scan state. While the blast radius is low (only scan session data is lost, not system or game data), the operation is not reversible — cleared scan results cannot be recovered. It fits Destructive as it permanently removes in-session data.

From the tool's definition Clear current scan results and reset scan state

Documented attack patterns abuse exactly the kind of access clear_scan gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Frida Game Hacking MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_scan:

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

clear_scan disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Frida Game Hacking MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the clear_scan tool do? +

Clear current scan results and reset scan state. It is categorised as a Destructive tool in the Frida Game Hacking MCP 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_scan? +

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

What risk level is clear_scan? +

clear_scan 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_scan? +

Yes. Add a rate_limit block to the clear_scan 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_scan completely? +

Set action: deny in the PolicyLayer policy for clear_scan. 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_scan? +

clear_scan is provided by the Frida Game Hacking MCP server (0xhackerfren/frida-game-hacking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frida Game Hacking MCP tool call.

Deterministic rules across all 42 Frida Game Hacking MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

42 Frida Game Hacking MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.