upscale_creative
AI agents invoke upscale_creative to trigger actions in Bedrock Image. 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.
The description is empty, so classification relies on the tool name and server context. 'Upscale_creative' likely performs AI-based creative upscaling of images using AWS Bedrock/Stability AI models, which is an external API operation that transforms data. This fits Execute (triggers external operations).
From the tool's definition Tool name 'upscale_creative' on a server described as providing image generation, editing, and manipulation via Stability AI on AWS Bedrock. Sibling tools include upscale_fast, generate_image, edit operations.
Attacks that exploit this kind of access
upscale_creative. It is categorised as a Execute tool in the Bedrock Image MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bedrock Image MCP server in PolicyLayer and add a rule for upscale_creative: 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.
upscale_creative 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 upscale_creative 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 upscale_creative. 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.
upscale_creative is provided by the Bedrock Image MCP server (yaksh36/mcp-server-bedrock-image). 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 →