Medium Risk

save_screenshot

Save a full-quality PNG screenshot to disk. Use this when you need a high-quality image for reporting, debugging, or sharing — not for LLM processing (use get_screenshot instead).

Accepts file system path (path)

Part of the Mobai MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mobai-mcp Write Risk 3/5

AI agents use save_screenshot to create or modify resources in Mobai. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call save_screenshot repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mobai.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-mobai-app-mobai-mcp.yaml
tools:
  save_screenshot:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mobai policy for all 23 tools.

Tool Name save_screenshot
Category Write
MCP Server Mobai MCP Server
Risk Level Medium

View all 23 tools →

Agents calling write-class tools like save_screenshot have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the save_screenshot tool do? +

Save a full-quality PNG screenshot to disk. Use this when you need a high-quality image for reporting, debugging, or sharing — not for LLM processing (use get_screenshot instead).. It is categorised as a Write tool in the Mobai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_screenshot? +

Add a rule in your Intercept YAML policy under the tools section for save_screenshot. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mobai MCP server.

What risk level is save_screenshot? +

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

Can I rate-limit save_screenshot? +

Yes. Add a rate_limit block to the save_screenshot rule in your Intercept 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 save_screenshot completely? +

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

save_screenshot is provided by the Mobai MCP server (mobai-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mobai

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.