AI agents call surface-flinger 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.
This tool reads and displays system state information about the device's graphics layers (SurfaceFlinger is Android's graphics composition system). It performs a retrieval operation only—no data is modified, deleted, executed, or compromised. This is consistent with other Read-category tools in the sibling list like 'battery-info', 'cpu-info', and 'display-info' which all query device state information.
From the tool's definition Tool name 'surface-flinger' and description '展示当前设备的图层信息' (display current device layer information) indicates a query/display operation that retrieves system graphics layer information without modification or side effects.
Documented attack patterns abuse exactly the kind of access surface-flinger gives an agent:
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 surface-flinger:
{
"version": "1",
"default": "deny",
"tools": {
"surface-flinger": {}
}
}surface-flinger 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.
展示当前设备的图层信息. It is categorised as a Read tool in the ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for surface-flinger: 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.
surface-flinger 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 surface-flinger 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 surface-flinger. 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.
surface-flinger 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.
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.