install_remotion_project
Install a reviewed Remotion project
This record as markdown: /tools/cutpilot/install-remotion-project.md
What install_remotion_project does on Cutpilot
AI agents invoke install_remotion_project 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 install_remotion_project is rated High
Installing a project involves executing package managers, writing files to disk, and potentially running setup scripts. While it involves writing files, the primary action is executing an installation process (e.g., npm install, project scaffolding) whose side effects depend on the project contents. This goes beyond simple Write as it triggers external operations and code execution.
From the tool's definition "Install a reviewed Remotion project" — the word 'install' indicates executing an installation process that sets up files, dependencies, and project structures on the local system
Attacks that exploit this kind of access
The rule that runs install_remotion_project 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 install_remotion_project, this is the rule to start with:
install_remotion_project 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 install_remotion_project call is checked against it from then on.
Questions about install_remotion_project
Install a reviewed Remotion project. 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 install_remotion_project: 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.
install_remotion_project 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 install_remotion_project 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 install_remotion_project. 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.
install_remotion_project 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