generate_image_sd35
AI agents use generate_image_sd35 to create or update resources in Bedrock Image — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bedrock Image environment.
The 'sd35' suffix strongly suggests Stable Diffusion 3.5, and the server context indicates this tool generates images. Image generation is a Write operation (creates new data). The description is empty, lowering confidence slightly, but the naming pattern and server context are clear. Severity is medium as misuse could generate inappropriate content or incur AWS costs.
From the tool's definition Tool name 'generate_image_sd35' alongside sibling tools like 'generate_image', 'generate_image_with_colors' on a server described as generating and editing images using Stable Diffusion 3.5 Large through Amazon Bedrock.
Attacks that exploit this kind of access
generate_image_sd35. It is categorised as a Write tool in the Bedrock Image MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bedrock Image MCP server in PolicyLayer and add a rule for generate_image_sd35: 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 Bedrock Image. Nothing to install.
generate_image_sd35 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_image_sd35 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_sd35. 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_sd35 is provided by the Bedrock Image MCP server (kalleeh/bedrock-image-mcp-server). 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 →