Génère une ou plusieurs images depuis un prompt texte via litmedia.ai. Retourne les URLs publiques des images générées.
AI agents invoke generate_image to trigger actions in Mcp Litmedia. 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 triggers an external AI image generation operation on litmedia.ai, producing externally hosted artifacts (public URLs). It is not a simple read/query, nor does it delete data or move money. It executes an external operation whose output depends on the prompt arguments, placing it firmly in Execute.
From the tool's definition Génère une ou plusieurs images depuis un prompt texte via litmedia.ai. Retourne les URLs publiques des images générées.
Attacks that exploit this kind of access
Génère une ou plusieurs images depuis un prompt texte via litmedia.ai. Retourne les URLs publiques des images générées. It is categorised as a Execute tool in the Mcp Litmedia MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Litmedia MCP server in PolicyLayer and add a rule for generate_image: 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 Mcp Litmedia. Nothing to install.
generate_image 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_image 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. 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 is provided by the Mcp Litmedia MCP server (para-fr/mcp-litmedia). 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 →