record_screen · Espresso MCP: Risk & Policy

WHAT IT DOES

What record_screen does on Espresso

AI agents use record_screen to create or update resources in Espresso — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Espresso environment.

WHY IT NEEDS A POLICY

Why record_screen needs a policy

An AI agent can call record_screen faster than any human can review — one bad instruction and it creates or modifies resources in Espresso by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_screen Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_screen": {
      "limits": [
        {
          "counter": "record_screen_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Espresso, so you can run agents against it safely.

FAQ

Questions about record_screen

What does the record_screen tool do? +

Record the screen of the connected Android device for a specified duration. It is categorised as a Write tool in the Espresso MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_screen? +

Register the Espresso MCP server in PolicyLayer and add a rule for record_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 Espresso. Nothing to install.

What risk level is record_screen? +

record_screen is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_screen? +

Yes. Add a rate_limit block to the record_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.

How do I block record_screen completely? +

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

What MCP server provides record_screen? +

record_screen is provided by the Espresso MCP server (vs4vijay/espresso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.