open_review_session
Start a token-protected localhost review UI for the real CutPilot project and optional rendered preview.
This record as markdown: /tools/cutpilot/open-review-session.md
What open_review_session does on Cutpilot
AI agents invoke open_review_session to trigger actions in Cutpilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why open_review_session is rated High
This tool launches a local web server/UI process, which constitutes executing an external operation. It starts a new service (localhost review UI) and optionally triggers rendering, both of which are side-effectful operations that go beyond mere data retrieval or modification. Severity is medium because it exposes a local network service, though it is token-protected.
From the tool's definition 'Start a token-protected localhost review UI' and 'optional rendered preview' — initiates a running process/service on the local machine
Attacks that exploit this kind of access
The rule that runs open_review_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open_review_session, this is the rule to start with:
open_review_session 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cutpilot, apply this rule, and every open_review_session call is checked against it from then on.
Questions about open_review_session
Start a token-protected localhost review UI for the real CutPilot project and optional rendered preview. It is categorised as a Execute tool in the Cutpilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cutpilot MCP server in PolicyLayer and add a rule for open_review_session: 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 Cutpilot. Nothing to install.
open_review_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_review_session 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 open_review_session. 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.
open_review_session is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cutpilot, and thousands of servers like it.
Across the catalogue