Skip to main content
Glama

adb_selinux_denials

List recent SELinux AVC denials from logcat and kernel logs to see which processes were blocked, what they attempted, and which contexts were involved when diagnosing permission issues.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_selinux_denials"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoMax denial entries to return (1-1000, default 50)
deviceNoDevice serial
processNoFilter denials by process/source context name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It discloses the log sources and the shape of what is returned (blocked process, attempted action, contexts), which is real added value, but it says nothing about whether root is required to read kernel logs, whether results are truncated, or how far back 'recent' reaches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and source. The closing 'useful for' sentence is the only soft padding, and even it carries diagnostic context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully summarizes the fields an agent will see, and all three parameters are documented in the schema. The missing piece is the operational prerequisite — whether elevated privileges are needed to read kernel-side denials.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with lines (range/default) and process filtering already documented. The description adds no extra semantics about how the process filter matches context names or how lines interacts with device selection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List recent SELinux AVC denial messages') and names the two data sources (logcat and kernel logs). It does not distinguish itself from the close sibling adb_selinux_status, which an agent would plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful for diagnosing permission issues and understanding security policy enforcement' implies when to reach for it, but there are no explicit exclusions and no pointer to alternatives such as adb_selinux_status (policy mode) or adb_permission_audit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools