adb_selinux_enable

Sets SELinux to Enforcing mode (enabled).

SERVERRenef SOURCEahmeth4n/renef-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ahmeth4n-renef-mcp/adb-selinux-enable.md

WHAT IT DOES

What adb_selinux_enable does on Renef

AI agents invoke adb_selinux_enable to trigger actions in Renef. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why adb_selinux_enable is rated High

This tool modifies the kernel security enforcement mode of an Android device by enabling SELinux enforcing mode. It triggers an external system-level operation that changes the device's security policy enforcement state. While it re-enables a security control (rather than disabling it), it still executes a privileged system command that alters device security configuration.

From the tool's definition Sets SELinux to Enforcing mode (enabled)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_selinux_enable 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 adb_selinux_enable, this is the rule to start with:

adb_selinux_enable Rate-limited

adb_selinux_enable stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_selinux_enable": {
      "limits": [
        {
          "counter": "adb_selinux_enable_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about adb_selinux_enable

What does the adb_selinux_enable tool do? +

Sets SELinux to Enforcing mode (enabled). It is categorised as a Execute tool in the Renef MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adb_selinux_enable? +

Register the Renef MCP server in PolicyLayer and add a rule for adb_selinux_enable: 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 adb_selinux_enable? +

adb_selinux_enable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adb_selinux_enable? +

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

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

adb_selinux_enable 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 → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →