annotate_assets
Store Codex-authored visual descriptions and tags after contact-sheet inspection.
This record as markdown: /tools/cutpilot/annotate-assets.md
What annotate_assets does on Cutpilot
AI agents use annotate_assets 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 annotate_assets is rated Medium
An AI agent can call annotate_assets faster than any human can review: one bad instruction and it creates or modifies resources in Cutpilot by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs annotate_assets 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 annotate_assets, this is the rule to start with:
annotate_assets 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 annotate_assets call is checked against it from then on.
Questions about annotate_assets
Store Codex-authored visual descriptions and tags after contact-sheet inspection. 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 annotate_assets: 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.
annotate_assets 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 annotate_assets 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 annotate_assets. 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.
annotate_assets 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