higgsfield_get_status
Check the status of a Higgsfield generation by ID. Prefers the customer's connected Higgsfield MCP account login; api_key is only the Cloud API fallback.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/higgsfield-get-status.md
What higgsfield_get_status does on UnClick
AI agents call higgsfield_get_status to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | Optional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available. |
generation_id | string | Yes | Generation ID returned by higgsfield_generate_video or higgsfield_generate_image |
Parameters from the server's own tool schema.
Why higgsfield_get_status is rated Low
This tool retrieves the status of a generation by ID, which is a read-only operation. It queries data from the Higgsfield service (either via user's connected account or API key fallback) and returns information. There are no side effects, no code execution, no data modification, and no destructive or financial implications. The use of 'check' and 'get_status' confirms this is a safe information retrieval tool.
From the tool's definition Tool name 'get_status' and description 'Check the status of a Higgsfield generation by ID' indicate a query operation that retrieves status information without modifying or executing operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs higgsfield_get_status 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 higgsfield_get_status, this is the rule to start with:
higgsfield_get_status is read-only, so it stays allowed. 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 higgsfield_get_status call is checked against it from then on.
Questions about higgsfield_get_status
Check the status of a Higgsfield generation by ID. Prefers the customer's connected Higgsfield MCP account login; api_key is only the Cloud API fallback. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
higgsfield_get_status accepts 2 parameters: api_key, generation_id. Required: generation_id. 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_get_status: 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_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the higgsfield_get_status 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_get_status. 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_get_status 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.
This server
Across the catalogue