stop_screenshot_recording

THE RISK

High Risk

Why stop_screenshot_recording needs a policy

This tool modifies the execution state of the Solar2D simulator by terminating a screenshot recording session. This is more than a passive read operation—it actively intervenes in an ongoing process. However, the impact is limited to screenshot recording (non-destructive and local to the development environment), making it Execute rather than Destructive.

From the tool's definition The tool 'stop_screenshot_recording' stops an active recording process. While not a direct command execution, it controls the state of a running operation within the Solar2D simulator environment.

Documented attack patterns abuse exactly the kind of access stop_screenshot_recording gives an agent:

POLICY

How to control stop_screenshot_recording

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 stop_screenshot_recording:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_screenshot_recording": {
      "limits": [
        {
          "counter": "stop_screenshot_recording_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

stop_screenshot_recording stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Solar2D MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Solar2D MCP Server tools

Execute run_solar2d_project Run a Solar2D project in the simulator. Provide either a path to main.lua or a project dir Execute start_screenshot_recording Start recording screenshots from the Solar2D simulator. Screenshots are captured every 100 Execute preview_social_post Generate an HTML preview of a social media post showing how it will appear on each platfor Execute simulate_drag Simulate a drag/swipe gesture in the Solar2D simulator. Specify start and end bounding box Execute simulate_tap Simulate a tap/click in the Solar2D simulator. Specify a bounding box using percentages an Write attach_to_trello_card Attach a file or Solar2D simulator screenshot to a Trello card. Write comment_trello_card Add a comment to a Trello card. Useful for logging progress, results, or notes. Write configure_social_media Configure social media posting via Late (getlate.dev). Save your Late API key to enable po

All 22 Solar2D MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Solar2D MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about stop_screenshot_recording

What does the stop_screenshot_recording tool do? +

Stop screenshot recording early. It is categorised as a Execute tool in the Solar2D MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_screenshot_recording? +

Register the Solar2D MCP Server MCP server in PolicyLayer and add a rule for stop_screenshot_recording: 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.

What risk level is stop_screenshot_recording? +

stop_screenshot_recording is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_screenshot_recording? +

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

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

stop_screenshot_recording 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.

Enforce policy on every Solar2D MCP Server tool call.

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.

CHECK YOUR STACK →