adb_logcat_query

Capture and filter Android logcat output in-process without shell grep pipelines.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/adb-logcat-query.md

WHAT IT DOES

What adb_logcat_query does on Jshookmcp

AI agents call adb_logcat_query to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why adb_logcat_query is rated Low

Retrieves device logs which may contain sensitive data but does not modify system state.

From the tool's definition Capture and filter Android logcat output; in-process, no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_logcat_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_logcat_query, this is the rule to start with:

adb_logcat_query Allowed

adb_logcat_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_logcat_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every adb_logcat_query call is checked against it from then on.

FAQ

Questions about adb_logcat_query

What does the adb_logcat_query tool do? +

Capture and filter Android logcat output in-process without shell grep pipelines. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_logcat_query? +

Register the Jshook MCP server in PolicyLayer and add a rule for adb_logcat_query: 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 Jshookmcp. Nothing to install.

What risk level is adb_logcat_query? +

adb_logcat_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_logcat_query? +

Yes. Add a rate_limit block to the adb_logcat_query 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.

How do I block adb_logcat_query completely? +

Set action: deny in the PolicyLayer policy for adb_logcat_query. 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.

What MCP server provides adb_logcat_query? +

adb_logcat_query is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →