List all available screenshots from the Solar2D simulator.
AI agents call list_screenshots to retrieve information from Solar2D MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates screenshot artifacts from a simulator without modifying, deleting, or executing any code. It is a passive information-gathering operation. Severity is low because screenshots of a game development project pose minimal security risk even if disclosed; the blast radius of misuse is limited to information exposure of visual assets.
From the tool's definition Tool name 'list_screenshots' and description 'List all available screenshots from the Solar2D simulator' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a read-only action that queries existing data.
Documented attack patterns abuse exactly the kind of access list_screenshots gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Solar2D MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_screenshots:
{
"version": "1",
"default": "deny",
"tools": {
"list_screenshots": {}
}
} list_screenshots is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available screenshots from the Solar2D simulator. It is categorised as a Read tool in the Solar2D MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Solar2D MCP Server 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 Solar2D MCP Server. 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 Solar2D MCP Server MCP server (sensiblecoder/solar2d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Solar2D MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Solar2D MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.