screen_save_region · Optic MCP: Risk & Policy

WHAT IT DOES

What screen_save_region does on OpticMCP

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

WHY IT NEEDS A POLICY

Why screen_save_region needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

screen_save_region Rate-limited

screen_save_region 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": {
    "screen_save_region": {
      "limits": [
        {
          "counter": "screen_save_region_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 OpticMCP, so you can run agents against it safely.

FAQ

Questions about screen_save_region

What does the screen_save_region tool do? +

screen_save_region. It is categorised as a Write tool in the OpticMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on screen_save_region? +

Register the Optic MCP server in PolicyLayer and add a rule for screen_save_region: 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 OpticMCP. Nothing to install.

What risk level is screen_save_region? +

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

Can I rate-limit screen_save_region? +

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

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

screen_save_region is provided by the Optic MCP server (timorleiderman/opticmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.