AI agents invoke gemini_prompt to trigger actions in Geminicli. 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 external code/operations (a Gemini CLI invocation) whose effects are contingent on the prompt argument supplied by the caller. While the Gemini model itself is trusted infrastructure, the tool enables arbitrary prompt injection and execution of generative AI operations that can produce unpredictable outputs.
From the tool's definition Tool invokes Gemini CLI with arbitrary prompts and executes them via the MCP server ("Invoke the headless Gemini CLI", "Runs in the MCP server"). The prompt content is user-controlled and will be processed by an external AI model.
Attacks that exploit this kind of access
Invoke the headless Gemini CLI with a single prompt. Stateless — each call is an independent turn. Runs in the MCP server. It is categorised as a Execute tool in the Geminicli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Geminicli MCP server in PolicyLayer and add a rule for gemini_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 Geminicli. Nothing to install.
gemini_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 gemini_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 gemini_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.
gemini_prompt is provided by the Geminicli MCP server (trevoraspencer/geminicli-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 →