Generate text using Google Gemini. Provide a prompt and optional model name.
AI agents invoke ai_generate to trigger actions in Node Code Sandbox MCP. 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 external operation (calling Google Gemini's API) whose effects depend on the prompt argument. It is not a simple read/query of local data, but an active call to an external AI service. Misuse could lead to prompt injection, data exfiltration via crafted prompts, or unintended generation of harmful content.
From the tool's definition 'Generate text using Google Gemini' — triggers an external API call to Google Gemini with an arbitrary prompt
Attacks that exploit this kind of access
Generate text using Google Gemini. Provide a prompt and optional model name. It is categorised as a Execute tool in the Node Code Sandbox MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Node Code Sandbox MCP server in PolicyLayer and add a rule for ai_generate: 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 Node Code Sandbox MCP. Nothing to install.
ai_generate 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 ai_generate 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 ai_generate. 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.
ai_generate is provided by the Node Code Sandbox MCP server (mozicim/node-code-sandbox-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 →