adb_selinux_denials
List recent SELinux AVC denial messages from logcat and kernel logs. Shows which processes were blocked, what they tried to do, and the SELinux contexts involved. Useful for diagnosing permission issues and understanding security policy enforcement.
This record as markdown: /tools/io-github-fullread-deepadb/adb-selinux-denials.md
What adb_selinux_denials does on Deepadb
AI agents call adb_selinux_denials 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_denials is rated Low
adb_selinux_denials reads and queries existing log entries from logcat and kernel logs to surface SELinux denial events. This is a diagnostic/observational operation with no capability to modify system state, execute commands, delete data, or trigger external actions. It falls cleanly into the Read category (retrieve/query data with no side effects).
From the tool's definition Tool name and description indicate it 'List[s] recent SELinux AVC denial messages' and 'Shows which processes were blocked' — purely retrieving and displaying log data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs adb_selinux_denials 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_denials, this is the rule to start with:
adb_selinux_denials 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_denials call is checked against it from then on.
Questions about adb_selinux_denials
List recent SELinux AVC denial messages from logcat and kernel logs. Shows which processes were blocked, what they tried to do, and the SELinux contexts involved. Useful for diagnosing permission issues and understanding security policy enforcement. 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_denials: 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_denials 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_denials 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_denials. 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_denials 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