AI agents invoke text_to_image to trigger actions in ComfyUI MCP Server. 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.
Text-to-image generation in ComfyUI involves executing a potentially complex workflow that processes user-supplied prompts and triggers external inference. While the core action (image generation) is not inherently destructive or financial, it executes computation on system resources whose exact effects depend on the prompt provided.
From the tool's definition Tool name 'text_to_image' with sibling tools 'run_workflow_from_file' and 'run_workflow_from_json' on a ComfyUI integration server that 'generate[s] images' indicates this tool executes an image generation workflow with arbitrary user input (the text prompt).
Documented attack patterns abuse exactly the kind of access text_to_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ComfyUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for text_to_image:
{
"version": "1",
"default": "deny",
"tools": {
"text_to_image": {
"limits": [
{
"counter": "text_to_image_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}text_to_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.
Free to start. No card required.
text_to_image. It is categorised as a Execute tool in the ComfyUI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ComfyUI MCP Server MCP server in PolicyLayer and add a rule for text_to_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 ComfyUI MCP Server. Nothing to install.
text_to_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 text_to_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 text_to_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.
text_to_image is provided by the ComfyUI MCP Server MCP server (overseer66/comfyui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ComfyUI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 ComfyUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.