Read logcat output filtered by manual tags or app profile tags.
AI agents call android_read_logcat to retrieve information from DevLab MCP Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads diagnostic log data from Android devices without modifying, executing commands, or causing side effects. It is purely a data retrieval operation with no capability to alter system state or trigger external operations. The filtering mechanism is passive query-based functionality.
From the tool's definition Tool name contains 'read' and description states 'Read logcat output filtered by manual tags or app profile tags.' Logcat is Android's logging system that outputs diagnostic information.
Attacks that exploit this kind of access
Read logcat output filtered by manual tags or app profile tags. It is categorised as a Read tool in the DevLab MCP Suite MCP Server, which means it retrieves data without modifying state.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_read_logcat: 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 DevLab MCP Suite. Nothing to install.
android_read_logcat 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 android_read_logcat 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 android_read_logcat. 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.
android_read_logcat is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →