clear_scan
Clear current scan results and reset scan state.
This record as markdown: /tools/0xhackerfren-frida-game-hacking-mcp/clear-scan.md
What clear_scan does on Frida Game Hacking MCP
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.
Why clear_scan is rated Critical
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
Attacks that exploit this kind of access
The rule that runs clear_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frida Game Hacking MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_scan, this is the rule to start with:
clear_scan is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Frida Game Hacking MCP, apply this rule, and every clear_scan call is checked against it from then on.
Questions about clear_scan
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.
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.
clear_scan 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_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.
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.
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.
More on Frida Game Hacking, and thousands of servers like it.
Across the catalogue