renef_hard_reset

A destructive tool on the Renef MCP server.

SERVERRenef SOURCEahmeth4n/renef-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ahmeth4n-renef-mcp/renef-hard-reset.md

WHAT IT DOES

What renef_hard_reset does on Renef

AI agents call renef_hard_reset to permanently remove resources in Renef, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why renef_hard_reset is rated Critical

Hard reset operations cannot be undone and result in complete loss of device state and data. This is irreversible destruction, making it Destructive rather than Execute. Although the description is empty, the tool name combined with the Android instrumentation context provides sufficient evidence.

From the tool's definition Tool name 'renef_hard_reset' combined with server context describing 'dynamic instrumentation and reverse engineering capabilities' and sibling tools that manage Android device state (adb_root_status, adb_selinux_disable, etc.).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs renef_hard_reset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Renef, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For renef_hard_reset, this is the rule to start with:

renef_hard_reset Hidden

renef_hard_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "renef_hard_reset"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Renef, apply this rule, and every renef_hard_reset call is checked against it from then on.

FAQ

Questions about renef_hard_reset

What does the renef_hard_reset tool do? +

renef_hard_reset is a destructive tool on the Renef MCP server. It is categorised as a Destructive tool in the Renef 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 renef_hard_reset? +

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

What risk level is renef_hard_reset? +

renef_hard_reset 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 renef_hard_reset? +

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

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

renef_hard_reset is provided by the Renef MCP server (ahmeth4n/renef-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Renef, and thousands of servers like it.

This server

All 75 Renef tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →