configure_screenshots · PyMOL-MCP-Vis MCP: Risk & Policy

WHAT IT DOES

What configure_screenshots does on PyMOL-MCP-Vis

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

WHY IT NEEDS A POLICY

Why configure_screenshots needs a policy

This tool writes to configuration state by adjusting when screenshots are automatically cleaned up. It is reversible (the threshold can be changed again) and has no destructive or side-effect-dependent execution characteristics. It does not read external data (Read), execute arbitrary code (Execute), irreversibly delete data (Destructive), or move money (Financial).

From the tool's definition Tool modifies screenshot auto-cleanup threshold, which is a configuration setting (reversible write operation). The description states 'Configure screenshot auto-cleanup threshold' - a clear modification of settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_screenshots Rate-limited

configure_screenshots 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": {
    "configure_screenshots": {
      "limits": [
        {
          "counter": "configure_screenshots_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 PyMOL-MCP-Vis, so you can run agents against it safely.

FAQ

Questions about configure_screenshots

What does the configure_screenshots tool do? +

Configure screenshot auto-cleanup threshold. It is categorised as a Write tool in the PyMOL-MCP-Vis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on configure_screenshots? +

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

What risk level is configure_screenshots? +

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

Can I rate-limit configure_screenshots? +

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

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

configure_screenshots is provided by the PyMOL-MCP-Vis MCP server (ryannmperez/pymol-mcp-vis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.