This record as markdown: /tools/io-github-portel-dev-ncp/generate-rendition.md
What generate_rendition does on Ncp
AI agents invoke generate_rendition to trigger actions in Ncp. 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 generate_rendition is rated High
This tool executes an external API call to Adobe services to generate an image rendition. It does not merely read existing data, nor does it irreversibly delete anything. It creates a derived artifact (a rendition) by invoking a third-party service, which classifies it as Execute. Severity is medium because misuse could incur API costs or generate unwanted content, but blast radius is limited.
From the tool's definition 'Generate image rendition using Adobe APIs' — triggers an external operation (calling Adobe APIs to process/render an image)
Attacks that exploit this kind of access
The rule that runs generate_rendition safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_rendition, this is the rule to start with:
generate_rendition 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 Ncp, apply this rule, and every generate_rendition call is checked against it from then on.
Questions about generate_rendition
Generate image rendition using Adobe APIs. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ncp MCP server in PolicyLayer and add a rule for generate_rendition: 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 Ncp. Nothing to install.
generate_rendition 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 generate_rendition 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 generate_rendition. 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.
generate_rendition is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue