get_device_info

Get comprehensive device information for forensic documentation

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/get-device-info.md

WHAT IT DOES

What get_device_info does on Android Forensics ADB MCP Server

AI agents call get_device_info 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 get_device_info is rated Low

This tool retrieves device metadata and configuration details without altering system state or executing commands with side effects. While the Android Forensics ADB context involves sensitive data access, this specific tool is a read operation.

From the tool's definition Tool name 'get_device_info' and description 'Get comprehensive device information for forensic documentation' indicate data retrieval with no modification. The tool queries device properties and system information for investigative purposes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_device_info 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 get_device_info, this is the rule to start with:

get_device_info Allowed

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

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 get_device_info call is checked against it from then on.

FAQ

Questions about get_device_info

What does the get_device_info tool do? +

Get comprehensive device information for forensic documentation. 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 get_device_info? +

Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for get_device_info: 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 get_device_info? +

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

Can I rate-limit get_device_info? +

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

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

get_device_info 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

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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