Capture screenshot of current PyMOL view at specified resolution.
AI agents call take_screenshot to retrieve information from PyMOL-MCP-Vis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots are non-destructive read operations that retrieve visual information about the current state of PyMOL. While PyMOL itself may be executing complex visualization operations, this tool merely observes and captures the result. No data is created, modified, deleted, or financial transactions involved. The screenshot capability serves as visual feedback for verification, a pure observation function.
From the tool's definition Tool captures screenshot of current PyMOL view. No modification to underlying data or state occurs. Descriptive verb 'capture' indicates retrieval of visual state without side effects.
Attacks that exploit this kind of access
Capture screenshot of current PyMOL view at specified resolution. It is categorised as a Read tool in the PyMOL-MCP-Vis MCP Server, which means it retrieves data without modifying state.
Register the PyMOL-MCP-Vis MCP server in PolicyLayer and add a rule for take_screenshot: 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.
take_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the take_screenshot 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 take_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.
take_screenshot 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →