plan_wedding_director
Create a non-mutating wedding-film plan for preparation, ceremony, portraits, speeches, and reception using annotated local media, transcribed vows, music, explicit gaps, and full/highlight variants.
This record as markdown: /tools/cutpilot/plan-wedding-director.md
What plan_wedding_director does on Cutpilot
AI agents call plan_wedding_director 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 plan_wedding_director is rated Low
The tool generates a planning/analysis artifact (a wedding film plan) without modifying any data. 'Non-mutating' confirms it is a read/analysis operation. It annotates and analyzes local media, transcriptions, and music to produce a plan, but does not write, execute, or delete anything.
From the tool's definition "Create a non-mutating wedding-film plan" — explicitly states it is non-mutating, indicating no side effects or data modification
Attacks that exploit this kind of access
The rule that runs plan_wedding_director 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 plan_wedding_director, this is the rule to start with:
plan_wedding_director 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 plan_wedding_director call is checked against it from then on.
Questions about plan_wedding_director
Create a non-mutating wedding-film plan for preparation, ceremony, portraits, speeches, and reception using annotated local media, transcribed vows, music, explicit gaps, and full/highlight variants. 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 plan_wedding_director: 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.
plan_wedding_director 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 plan_wedding_director 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 plan_wedding_director. 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.
plan_wedding_director 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