system_webview
Inspect WebView via Chrome DevTools Protocol (Android only)
This record as markdown: /tools/alexgladkov-claude-in-mobile/system-webview.md
What system_webview does on Claude Mobile
AI agents call system_webview to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why system_webview is rated Low
The tool is described as 'Inspect' which implies reading/querying the WebView state via Chrome DevTools Protocol. However, CDP can also execute JavaScript and perform write/execute operations, but the description only mentions inspection. Confidence is moderate because CDP access could enable execute-level capabilities not explicitly described.
From the tool's definition Inspect WebView via Chrome DevTools Protocol
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_webview safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_webview, this is the rule to start with:
system_webview is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every system_webview call is checked against it from then on.
Questions about system_webview
Inspect WebView via Chrome DevTools Protocol (Android only). It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for system_webview: 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 Claude Mobile. Nothing to install.
system_webview 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 system_webview 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 system_webview. 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.
system_webview is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
This server
Across the catalogue