adb_logcat
Capture logcat output (dump mode). Use filters like 'ActivityManager:I *:S'.
This record as markdown: /tools/1shin-7-ya-frida-mcp/adb-logcat.md
What adb_logcat does on Ya Frida
AI agents call adb_logcat to retrieve information from Ya Frida without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_logcat is rated Low
Logcat is Android's logging mechanism. Reading logs retrieves existing diagnostic data with no side effects—no data is created, modified, deleted, or code executed as a result of this operation. While logs may contain sensitive information (increasing information disclosure risk), the tool itself performs only a Read operation.
From the tool's definition The tool 'adb_logcat' is described as 'Capture logcat output (dump mode)' with filter examples. The verb 'capture' and 'dump mode' indicate reading/retrieving log data without modifying system state.
Attacks that exploit this kind of access
The rule that runs adb_logcat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ya Frida, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_logcat, this is the rule to start with:
adb_logcat 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 Ya Frida, apply this rule, and every adb_logcat call is checked against it from then on.
Questions about adb_logcat
Capture logcat output (dump mode). Use filters like 'ActivityManager:I *:S'. It is categorised as a Read tool in the Ya Frida MCP Server, which means it retrieves data without modifying state.
Register the Ya Frida MCP server in PolicyLayer and add a rule for adb_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 Ya Frida. Nothing to install.
adb_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 adb_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 adb_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.
adb_logcat is provided by the Ya Frida MCP server (1shin-7/ya-frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ya Frida, and thousands of servers like it.
This server
Across the catalogue