generate_image
Generate images from text prompts using Kling AI. Create high-quality images with multiple aspect ratios and optional character reference support. Supports models v1, v1.5, and v2 with customizable parameters for creative control.
This record as markdown: /tools/199-mcp-mcp-kling/generate-image.md
What generate_image does on MCP Kling
AI agents invoke generate_image to trigger actions in MCP Kling. 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.
Why generate_image is rated High
This tool triggers an external AI image generation operation via Kling AI's service. It is not a simple data write (no local data is created/modified by the caller) but rather executes an external operation whose effects depend on the arguments (prompt, model, parameters). It falls under Execute as it invokes an external computation/generation pipeline.
From the tool's definition Generate images from text prompts using Kling AI... Supports models v1, v1.5, and v2 with customizable parameters
Attacks that exploit this kind of access
The rule that runs generate_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Kling, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_image, this is the rule to start with:
generate_image stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Kling, apply this rule, and every generate_image call is checked against it from then on.
Questions about generate_image
Generate images from text prompts using Kling AI. Create high-quality images with multiple aspect ratios and optional character reference support. Supports models v1, v1.5, and v2 with customizable parameters for creative control. It is categorised as a Execute tool in the MCP Kling MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kling MCP server in PolicyLayer and add a rule for 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 MCP Kling. Nothing to install.
generate_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
generate_image is provided by the MCP Kling MCP server (199-mcp/mcp-kling). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Kling, and thousands of servers like it.
Across the catalogue