adb_selinux_status

Shows the current SELinux status on the Android device.

SERVERRenef SOURCEahmeth4n/renef-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What adb_selinux_status does on Renef

AI agents call adb_selinux_status to retrieve information from Renef without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why adb_selinux_status is rated Low

This tool retrieves the current SELinux enforcement mode (enforcing/permissive/disabled) on the Android device via ADB. It is a read-only query with no side effects, modifications, or external operations triggered. The low severity reflects minimal risk even if an AI agent misuses it—it only exposes security policy state information.

From the tool's definition Tool name 'adb_selinux_status' and description 'Shows the current SELinux status' indicate a query operation that retrieves information about the device's security context without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adb_selinux_status Allowed

adb_selinux_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_selinux_status": {}
  }
}

ALLOW ONLY 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_status call is checked against it from then on.

FAQ

Questions about adb_selinux_status

What does the adb_selinux_status tool do? +

Shows the current SELinux status on the Android device. It is categorised as a Read tool in the Renef MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_selinux_status? +

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

adb_selinux_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_selinux_status? +

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

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

adb_selinux_status 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 →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →