read_project
Read a CutPilot project, its assets, tracks, items, captions, markers, and validation state.
This record as markdown: /tools/cutpilot/read-project.md
What read_project does on Cutpilot
AI agents call read_project to retrieve information from Cutpilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_project is rated Low
This tool performs data retrieval only. It queries and returns information about an existing project and its components without creating, modifying, deleting, or executing any operations.
From the tool's definition Tool name is 'read_project' and description explicitly states 'Read a CutPilot project' — retrieves project structure, assets, tracks, items, captions, markers, and validation state with no side effects.
Attacks that exploit this kind of access
The rule that runs read_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 read_project, this is the rule to start with:
read_project is read-only, so it stays allowed. 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 read_project call is checked against it from then on.
Questions about read_project
Read a CutPilot project, its assets, tracks, items, captions, markers, and validation state. It is categorised as a Read tool in the Cutpilot MCP Server, which means it retrieves data without modifying state.
Register the Cutpilot MCP server in PolicyLayer and add a rule for read_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.
read_project 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 read_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 read_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.
read_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.
This server
Across the catalogue