screen
Screen capture and annotation. capture: screenshot with compression/diff. annotate: screenshot with element bounding boxes.
This record as markdown: /tools/alexgladkov-claude-in-mobile/screen.md
What screen does on Claude Mobile
AI agents use screen to create or update resources in Claude Mobile, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Mobile environment.
Why screen is rated Medium
An AI agent can call screen faster than any human can review: one bad instruction and it creates or modifies resources in Claude Mobile by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs screen 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 screen, this is the rule to start with:
screen stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 screen call is checked against it from then on.
Questions about screen
Screen capture and annotation. capture: screenshot with compression/diff. annotate: screenshot with element bounding boxes. It is categorised as a Write tool in the Claude Mobile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for screen: 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.
screen is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the screen 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 screen. 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.
screen 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