generate_images
AI agents use generate_images to create or update resources in Jimeng Image MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jimeng Image MCP Server environment.
The tool name and server context strongly suggest this tool generates AI images and potentially stores them. Image generation creates new content (Write category). The empty description lowers confidence, but the server description mentioning persistent storage via Tencent Cloud COS implies the results may be saved remotely. No indication of destructive, financial, or execution behavior.
From the tool's definition Tool name 'generate_images' on a server described as providing 'AI image generation via Jimeng models' with 'optional persistent storage using Tencent Cloud COS'
Attacks that exploit this kind of access
generate_images. It is categorised as a Write tool in the Jimeng Image MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jimeng Image MCP Server MCP server in PolicyLayer and add a rule for generate_images: 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 Jimeng Image MCP Server. Nothing to install.
generate_images is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_images 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_images. 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_images is provided by the Jimeng Image MCP Server MCP server (nanguangchou/jimeng_image_mcp). 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 →