List all captured PyMOL screenshots in the current session.
AI agents call list_screenshots 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.
This tool queries and returns a list of existing screenshots. It performs no modifications, deletions, or external operations—purely a read operation to enumerate captured images. The low severity reflects minimal risk: an AI agent listing screenshots cannot cause harm through misuse of this tool alone.
From the tool's definition Tool name 'list_screenshots' and description 'List all captured PyMOL screenshots in the current session' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all captured PyMOL screenshots in the current session. 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 list_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.
list_screenshots 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 list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_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.
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 →