adb_selinux_status
Check SELinux enforcement mode, policy version, and recent denial count. Shows whether the device is in Enforcing, Permissive, or Disabled mode. Root access provides additional policy details from dmesg audit logs.
This record as markdown: /tools/io-github-fullread-deepadb/adb-selinux-status.md
What adb_selinux_status does on Deepadb
AI agents call adb_selinux_status to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_selinux_status is rated Low
This is a read-only diagnostic tool that queries system security settings without performing any actions that could modify, delete, or execute operations. While it accesses security-sensitive information (SELinux status), the blast radius of misuse is minimal—an agent cannot cause harm by reading this data.
From the tool's definition Tool description indicates it 'checks' and 'shows' SELinux status information—no creation, modification, deletion, or execution of commands.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_selinux_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_selinux_status call is checked against it from then on.
Questions about adb_selinux_status
Check SELinux enforcement mode, policy version, and recent denial count. Shows whether the device is in Enforcing, Permissive, or Disabled mode. Root access provides additional policy details from dmesg audit logs. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb 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 Deepadb. Nothing to install.
adb_selinux_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
adb_selinux_status is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue