higgsfield_get_styles
List Higgsfield models/styles. 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-styles.md
What higgsfield_get_styles does on UnClick
AI agents call higgsfield_get_styles 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 |
|---|---|---|---|
type | string | — | Model type to explore, e.g. image or video (default image) |
query | string | — | Optional model/style search text |
action | string | — | MCP model explorer action (default search) |
api_key | string | — | Optional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available. |
Parameters from the server's own tool schema.
Why higgsfield_get_styles is rated Low
This tool performs a read-only operation to list/retrieve available Higgsfield models and styles. It authenticates via a customer's account or API key but does not create, modify, delete, or execute any operations. The data retrieval has minimal blast radius if misused by an agent—it would only expose available style options without side effects.
From the tool's definition Tool name contains 'get_' and description states 'List Higgsfield models/styles', which retrieves data without modifying or deleting it.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs higgsfield_get_styles 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_styles, this is the rule to start with:
higgsfield_get_styles 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_styles call is checked against it from then on.
Questions about higgsfield_get_styles
List Higgsfield models/styles. 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_styles accepts 4 parameters: type, query, action, 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_get_styles: 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_styles 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_styles 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_styles. 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_styles 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