New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser

Browser automation. open/close/list_sessions: session management. navigate/click/fill/fill_form/press_key: interaction. snapshot/screenshot: capture. evaluate: run JS. wait_for_selector: wait for element.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/browser.md

What browser does on Claude Mobile

AI agents invoke browser to trigger actions in Claude Mobile. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why browser is rated High

The 'evaluate: run JS' capability demonstrates this tool can execute arbitrary code in the browser context, which classifies it as Execute rather than Write. While it also performs Read operations (screenshots) and Write operations (filling forms), the ability to execute JavaScript code represents the most severe capability.

From the tool's definition Tool enables browser automation with capabilities to 'navigate/click/fill/fill_form/press_key: interaction' and crucially 'evaluate: run JS' which allows execution of arbitrary JavaScript code.

Questions about browser

What does the browser tool do? +

Browser automation. open/close/list_sessions: session management. navigate/click/fill/fill_form/press_key: interaction. snapshot/screenshot: capture. evaluate: run JS. wait_for_selector: wait for element. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for browser: 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.

What risk level is browser? +

browser is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser? +

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

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

browser 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Mobile's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.