stability_list_engines
List all available Stability AI generation engines.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/stability-list-engines.md
What stability_list_engines does on UnClick
AI agents call stability_list_engines 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 | Yes |
Parameters from the server's own tool schema.
Why stability_list_engines is rated Low
This tool queries and returns information about available engines without creating, modifying, deleting, executing code, or affecting any state. It is a simple read operation to discover available resources.
From the tool's definition Tool name contains 'list' and description states 'List all available Stability AI generation engines', indicating a retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs stability_list_engines 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 stability_list_engines, this is the rule to start with:
stability_list_engines 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 stability_list_engines call is checked against it from then on.
Questions about stability_list_engines
List all available Stability AI generation engines. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
stability_list_engines accepts 1 parameter: api_key. Required: 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 stability_list_engines: 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.
stability_list_engines 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 stability_list_engines 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 stability_list_engines. 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.
stability_list_engines 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