New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

higgsfield_generate_image

Generate a Higgsfield image from a prompt. Prefers the customer's connected Higgsfield MCP account login and subscription credits; api_key is only the Cloud API fallback.

SERVERUnClick SOURCE@unclick/mcp-server
High RISK CLASS
Category Execute
Parameters 101 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/higgsfield-generate-image.md

What higgsfield_generate_image does on UnClick

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.

ParameterTypeRequiredDescription
seed number Random seed for reproducibility
model string Optional Higgsfield model id, e.g. nano_banana_pro
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 Optional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available.
resolution string Optional Higgsfield resolution, e.g. 1k, 2k, or 4k
aspect_ratio string e.g. 16:9, 4:3, 1:1, 9:16
negative_prompt string What to avoid in the image

Parameters from the server's own tool schema.

Why higgsfield_generate_image is rated High

This tool executes an image generation operation using an external AI service (Higgsfield), consuming subscription credits. It triggers an external operation with real-world resource consumption. It is not a simple read, nor does it delete data or move money, but it does run an external process and consume credits, placing it in Execute category.

From the tool's definition Generate a Higgsfield image from a prompt... uses subscription credits

Risk signalsHandles credentials or secrets (api_key) · High parameter count (10 properties)

Questions about higgsfield_generate_image

What does the higgsfield_generate_image tool do? +

Generate a Higgsfield image from a prompt. Prefers the customer's connected Higgsfield MCP account login and subscription credits; api_key is only the Cloud API fallback. 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.

What parameters does higgsfield_generate_image accept? +

higgsfield_generate_image accepts 10 parameters: seed, model, style, width, height, prompt, api_key, resolution, aspect_ratio, negative_prompt. Required: prompt. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on higgsfield_generate_image? +

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.

What risk level is higgsfield_generate_image? +

higgsfield_generate_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit higgsfield_generate_image? +

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.

How do I block higgsfield_generate_image completely? +

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.

What MCP server provides higgsfield_generate_image? +

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.

More on UnClick, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.