AI agents call higgsfield_get_status to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Higgsfield API key |
generation_id | string | Yes | Generation ID returned by higgsfield_generate_video or higgsfield_generate_image |
Parameters from the server's own tool schema.
The tool queries and returns information about an existing resource (AI generation status and video URL) without modifying, executing, or deleting anything. This is a straightforward read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'Check the status of a Higgsfield AI generation by ID. Returns status, video URL when complete.' — this is purely a retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Check the status of a Higgsfield AI generation by ID. Returns status, video URL when complete. 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: api_key, 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.
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 →