track_generation
Refresh a generation job or materialize its completed output into the CutPilot asset library.
This record as markdown: /tools/cutpilot/track-generation.md
What track_generation does on Cutpilot
AI agents use track_generation 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 track_generation is rated Medium
This tool modifies the asset library by materializing/storing generated output, which is a reversible write operation. It does not execute arbitrary code (Execute), irreversibly delete (Destructive), move money (Financial), or merely read data (Read). The medium severity reflects that misuse could pollute the asset library with unwanted generated content, though the effects are reversible.
From the tool's definition Tool description states it can 'materialize its completed output into the CutPilot asset library,' which creates or adds data to a system. The term 'materialize' indicates converting generated content into stored assets, a write operation.
Attacks that exploit this kind of access
The rule that runs track_generation 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 track_generation, this is the rule to start with:
track_generation 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 track_generation call is checked against it from then on.
Questions about track_generation
Refresh a generation job or materialize its completed output into the CutPilot asset library. 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 track_generation: 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.
track_generation 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 track_generation 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 track_generation. 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.
track_generation 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