[CodeLoop] You MUST call codeloop_verify after every code change. If .codeloop/config.json is missing, call codeloop_init_project FIRST. Capture a screenshot of the app window and save it for visual review. Use this tool when: - You want to capture a specific page/screen of the app for visual an...
Part of the Codeloop MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call codeloop_capture_screenshot to retrieve information from Codeloop without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though codeloop_capture_screenshot only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
codeloop_capture_screenshot:
rules:
- action: allowSee the full Codeloop policy for all 29 tools.
Agents calling read-class tools like codeloop_capture_screenshot have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
[CodeLoop] You MUST call codeloop_verify after every code change. If .codeloop/config.json is missing, call codeloop_init_project FIRST. Capture a screenshot of the app window and save it for visual review. Use this tool when: - You want to capture a specific page/screen of the app for visual analysis - You are navigating through the app to capture all pages for complete visual coverage - You want to add a screenshot to an existing verification run Provide app_name to capture ONLY that app's window (REQUIRED for correct capture). The app is automatically brought to the front before capture, and the IDE is restored to the front after. Without app_name, captures the full screen which may show the IDE instead of the app. Returns: confirmation + the captured image as an MCP ImageContent block so you can see what was captured.. It is categorised as a Read tool in the Codeloop MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for codeloop_capture_screenshot. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Codeloop MCP server.
codeloop_capture_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 codeloop_capture_screenshot rule in your Intercept 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 Intercept policy for codeloop_capture_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.
codeloop_capture_screenshot is provided by the Codeloop MCP server (codeloop-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.