Get device security configuration and status.
AI agents call get_device_security_status 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.
This tool queries and retrieves security configuration information from an Android device. It performs no side effects, does not execute commands, and does not alter device state or data. While the forensic context is sensitive, the tool itself is a passive information retrieval operation that falls squarely into the Read category.
From the tool's definition Tool name 'get_device_security_status' and description 'Get device security configuration and status' indicate data retrieval without modification. The verb 'Get' and absence of action keywords (create, delete, execute, modify) confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access get_device_security_status 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 get_device_security_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_security_status": {}
}
}get_device_security_status 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.
Get device security configuration and status. 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 get_device_security_status: 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.
get_device_security_status 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 get_device_security_status 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 get_device_security_status. 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.
get_device_security_status 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.