AI agents call parse_browser_history to retrieve information from Android Forensics ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly implies reading and parsing browser history data from an Android device. In the context of a forensics server focused on artifact collection, this is a data retrieval operation. No description is provided, which lowers confidence, but sibling tools like analyze_gmail and analyze_instagram suggest a pattern of read-only artifact analysis.
From the tool's definition Tool name 'parse_browser_history' and server context of Android forensics/artifact collection.
Documented attack patterns abuse exactly the kind of access parse_browser_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Forensics ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for parse_browser_history:
{
"version": "1",
"default": "deny",
"tools": {
"parse_browser_history": {}
}
}parse_browser_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
parse_browser_history. It is categorised as a Read tool in the Android Forensics ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for parse_browser_history: 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.
parse_browser_history 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 parse_browser_history 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 parse_browser_history. 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.
parse_browser_history 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.
Start from Android Forensics 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.
58 Android Forensics ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.