plan_explainer_director
Create a non-mutating narration-led explainer plan with semantic primary visuals, secondary evidence, explicit gaps, and pending fact-checkable information cards.
This record as markdown: /tools/cutpilot/plan-explainer-director.md
What plan_explainer_director does on Cutpilot
AI agents use plan_explainer_director to create or update resources in Cutpilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cutpilot environment.
Why plan_explainer_director is rated Medium
This tool generates new planning data (narration, visual mappings, information structures) that can be persisted and used in video editing workflows, making it a Write operation. It does not execute external commands or delete data (hence not Execute or Destructive).
From the tool's definition Tool creates a 'narration-led explainer plan' with 'semantic primary visuals, secondary evidence, and information cards.' The word 'create' and 'plan' indicate content generation.
Attacks that exploit this kind of access
The rule that runs plan_explainer_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_explainer_director, this is the rule to start with:
plan_explainer_director stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 plan_explainer_director call is checked against it from then on.
Questions about plan_explainer_director
Create a non-mutating narration-led explainer plan with semantic primary visuals, secondary evidence, explicit gaps, and pending fact-checkable information cards. It is categorised as a Write tool in the Cutpilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cutpilot MCP server in PolicyLayer and add a rule for plan_explainer_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_explainer_director is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plan_explainer_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_explainer_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_explainer_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