parse_call_log_db

Parse Android call log database (calllog.db or contacts2.db).

SERVERAndroid Forensics ADB MCP Server SOURCE0x-professor/droidforensics-suite

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/0x-professor-droidforensics-suite/parse-call-log-db.md

WHAT IT DOES

What parse_call_log_db does on Android Forensics ADB MCP Server

AI agents call parse_call_log_db to retrieve information from Android Forensics ADB MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why parse_call_log_db is rated Low

The tool parses/reads existing database files from Android devices to extract call log records. This is a read-only forensic data retrieval operation with no side effects. Severity is medium because call logs contain sensitive personal communications metadata (who called whom, when, duration), which could be privacy-sensitive if misused.

From the tool's definition Parse Android call log database (calllog.db or contacts2.db)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs parse_call_log_db safely

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

parse_call_log_db Allowed

parse_call_log_db 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": {
    "parse_call_log_db": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Android Forensics ADB MCP Server, apply this rule, and every parse_call_log_db call is checked against it from then on.

FAQ

Questions about parse_call_log_db

What does the parse_call_log_db tool do? +

Parse Android call log database (calllog.db or contacts2.db). It is categorised as a Read tool in the Android Forensics ADB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on parse_call_log_db? +

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

What risk level is parse_call_log_db? +

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

Can I rate-limit parse_call_log_db? +

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

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

parse_call_log_db is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Android Forensics ADB MCP Server, and thousands of servers like it.

This server

All 58 Android Forensics ADB MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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