generate_image
Generate an image from a text description using Apple Intelligence on-device image generation (Image Playground).
This record as markdown: /tools/io-github-heznpc-iconnect/generate-image.md
What generate_image does on Iconnect
AI agents invoke generate_image to trigger actions in Iconnect. 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_image is rated High
This tool triggers an on-device AI image generation process (Image Playground), which constitutes executing an external operation. It's not a simple read/write of existing data — it invokes a generative AI system to produce new content. Severity is medium as misuse could generate inappropriate imagery or consume significant device resources, but blast radius is limited to the local device.
From the tool's definition Generate an image from a text description using Apple Intelligence on-device image generation (Image Playground)
Attacks that exploit this kind of access
The rule that runs generate_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_image, this is the rule to start with:
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 Iconnect, apply this rule, and every generate_image call is checked against it from then on.
Questions about generate_image
Generate an image from a text description using Apple Intelligence on-device image generation (Image Playground). It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for 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 Iconnect. Nothing to install.
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 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 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.
generate_image is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue