adb_selinux_disable
Sets SELinux to Permissive mode (disabled enforcement).
This record as markdown: /tools/ahmeth4n-renef-mcp/adb-selinux-disable.md
What adb_selinux_disable does on Renef
AI agents invoke adb_selinux_disable 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.
Why adb_selinux_disable is rated High
Disabling SELinux enforcement is a security configuration change that weakens the Android device's mandatory access control, allowing processes to bypass security policies. This is an Execute-level action (running a privileged system command to change security state) with high severity since it exposes the entire device to elevated risk by removing kernel-level security enforcement.
From the tool's definition Sets SELinux to Permissive mode (disabled enforcement)
Attacks that exploit this kind of access
The rule that runs adb_selinux_disable 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_disable, this is the rule to start with:
adb_selinux_disable 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Renef, apply this rule, and every adb_selinux_disable call is checked against it from then on.
Questions about adb_selinux_disable
Sets SELinux to Permissive mode (disabled enforcement). 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.
Register the Renef MCP server in PolicyLayer and add a rule for adb_selinux_disable: 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.
adb_selinux_disable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_selinux_disable 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 adb_selinux_disable. 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.
adb_selinux_disable 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.
More on Renef, and thousands of servers like it.
This server
Across the catalogue