render_product_promo_cards
Render only reviewed product claims and CTA cards as safe editable SVG Motion Graphics on V3 Text & CTA.
This record as markdown: /tools/cutpilot/render-product-promo-cards.md
What render_product_promo_cards does on Cutpilot
AI agents invoke render_product_promo_cards to trigger actions in Cutpilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why render_product_promo_cards is rated High
The tool renders (executes a generation process) SVG motion graphics onto a specific timeline track (V3). This is an Execute-level action because it triggers an external rendering pipeline whose effects depend on the reviewed product claims and CTA content passed as arguments.
From the tool's definition 'Render' indicates triggering an external rendering operation; 'SVG Motion Graphics on V3 Text & CTA' indicates output is generated/written to a timeline layer
Attacks that exploit this kind of access
The rule that runs render_product_promo_cards 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 render_product_promo_cards, this is the rule to start with:
render_product_promo_cards stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 render_product_promo_cards call is checked against it from then on.
Questions about render_product_promo_cards
Render only reviewed product claims and CTA cards as safe editable SVG Motion Graphics on V3 Text & CTA. It is categorised as a Execute tool in the Cutpilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cutpilot MCP server in PolicyLayer and add a rule for render_product_promo_cards: 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.
render_product_promo_cards is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the render_product_promo_cards 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 render_product_promo_cards. 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.
render_product_promo_cards 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.
Across the catalogue