Low Risk

get-crash-log

获取应用崩溃日志,分析错误原因

How to control get-crash-log ↓

What get-crash-log does on ADB MCP Server

AI agents call get-crash-log to retrieve information from ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get-crash-log needs a policy

This tool retrieves and reads crash logs from Android applications. It performs no side effects, modifications, or destructive actions. Retrieving diagnostic logs is a read-only operation with minimal security impact—logs are typically non-sensitive debugging information. The low severity reflects that crash logs generally contain only error traces and stack information, not user data or system credentials.

From the tool's definition Tool name 'get-crash-log' and description '获取应用崩溃日志,分析错误原因' (get application crash logs, analyze error causes) indicate data retrieval without modification or system changes.

Documented attack patterns abuse exactly the kind of access get-crash-log gives an agent:

How to control get-crash-log

PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-crash-log:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-crash-log": {}
  }
}

get-crash-log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ADB MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get-crash-log

What does the get-crash-log tool do? +

获取应用崩溃日志,分析错误原因. It is categorised as a Read tool in the ADB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-crash-log? +

Register the ADB MCP Server MCP server in PolicyLayer and add a rule for get-crash-log: 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 ADB MCP Server. Nothing to install.

What risk level is get-crash-log? +

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

Can I rate-limit get-crash-log? +

Yes. Add a rate_limit block to the get-crash-log 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 get-crash-log completely? +

Set action: deny in the PolicyLayer policy for get-crash-log. 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 get-crash-log? +

get-crash-log is provided by the ADB MCP Server MCP server (jiantao88/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ADB MCP Server tool call.

Start from ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

30 ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.