直接调用火山方舟 Seedream API 生成图片(Ark-only)
AI agents invoke generate-img-seedream4 to trigger actions in Seedream/Seedance 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.
This tool invokes an external third-party API (Volcengine Ark) to generate images. It is not a simple read/query, nor does it delete data. It executes an external operation whose effects (image generation, possible API costs) depend on the input arguments, placing it in the Execute category.
From the tool's definition '生成图片' (generate image) by calling '火山方舟 Seedream API' (Volcengine Ark API) — triggers an external API operation that produces output depending on arguments
Attacks that exploit this kind of access
直接调用火山方舟 Seedream API 生成图片(Ark-only). It is categorised as a Execute tool in the Seedream/Seedance MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Seedream/Seedance MCP Server MCP server in PolicyLayer and add a rule for generate-img-seedream4: 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 Seedream/Seedance MCP Server. Nothing to install.
generate-img-seedream4 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-img-seedream4 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-img-seedream4. 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-img-seedream4 is provided by the Seedream/Seedance MCP Server MCP server (nsmao-com/seedream-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 →