Generate a preview image from a text prompt (no input image).
AI agents invoke vlm_test_prompt to trigger actions in Albumentations. 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 executes an image generation pipeline from a text prompt, triggering external processing (likely via a VLM/diffusion model). It does not merely read existing data nor write user-provided data — it runs an external operation whose output depends on the prompt argument. Severity is medium as misuse could generate inappropriate content or consume compute resources, but blast radius is limited.
From the tool's definition "Generate a preview image from a text prompt" — triggers external image generation operations based on input arguments
Attacks that exploit this kind of access
Generate a preview image from a text prompt (no input image). It is categorised as a Execute tool in the Albumentations MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Albumentations MCP server in PolicyLayer and add a rule for vlm_test_prompt: 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 Albumentations. Nothing to install.
vlm_test_prompt 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 vlm_test_prompt 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 vlm_test_prompt. 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.
vlm_test_prompt is provided by the Albumentations MCP server (ramsi-k/albumentations-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 →