openai_generate_image
Generate images from a text prompt using DALL-E.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/openai-generate-image.md
What openai_generate_image does on UnClick
AI agents invoke openai_generate_image to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
n | number | — | Number of images to generate |
size | string | — | 1024x1024, 1792x1024, or 1024x1792 for DALL-E 3 |
model | string | — | dall-e-3 or dall-e-2 (default: dall-e-3) |
style | string | — | natural or vivid (DALL-E 3 only) |
prompt | string | Yes | |
api_key | string | Yes | |
quality | string | — | standard or hd (DALL-E 3 only) |
Parameters from the server's own tool schema.
Why openai_generate_image is rated High
This tool triggers an external API call to OpenAI's DALL-E service to generate images. It executes an external operation with side effects (API usage, potential costs), placing it in the Execute category. It is not purely Read (it creates new content), but since it generates a new artifact rather than modifying existing data, Execute is the most appropriate category.
From the tool's definition Generate images from a text prompt using DALL-E
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs openai_generate_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openai_generate_image, this is the rule to start with:
openai_generate_image 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 UnClick, apply this rule, and every openai_generate_image call is checked against it from then on.
Questions about openai_generate_image
Generate images from a text prompt using DALL-E. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
openai_generate_image accepts 7 parameters: n, size, model, style, prompt, api_key, quality. Required: prompt, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for openai_generate_image: 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 UnClick. Nothing to install.
openai_generate_image 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 openai_generate_image 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 openai_generate_image. 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.
openai_generate_image is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue