AI agents invoke higgsfield_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 |
|---|---|---|---|
seed | number | — | Random seed for reproducibility |
style | string | — | Style name (use higgsfield_get_styles to list available styles) |
width | number | — | Image width in pixels |
height | number | — | Image height in pixels |
prompt | string | Yes | Text description of the image to generate |
api_key | string | Yes | Higgsfield API key |
negative_prompt | string | — | What to avoid in the image |
Parameters from the server's own tool schema.
This tool triggers an external AI service (Higgsfield AI) to generate images, constituting an external operation with side effects. It is not a simple read/query, and it initiates a computational process on an external platform, classifying it as Execute. Severity is medium as misuse could incur API costs or generate inappropriate content, but blast radius is limited.
From the tool's definition Generate an image from a text prompt using Higgsfield AI
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Generate an image from a text prompt using Higgsfield AI. 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.
higgsfield_generate_image accepts 7 parameters: seed, style, width, height, prompt, api_key, negative_prompt. 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 higgsfield_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.
higgsfield_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 higgsfield_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 higgsfield_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.
higgsfield_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →