run_gemini
AI agents invoke run_gemini to trigger actions in Gemini CLI MCP Server. 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.
Although the tool description is empty, the context strongly indicates this tool executes Gemini CLI prompts/commands. Execution tools pose high risk because their effects depend entirely on the prompt content supplied by an AI agent—the agent could invoke the Gemini CLI to perform arbitrary operations including data retrieval, modification, or damage depending on what the CLI supports.
From the tool's definition Tool name 'run_gemini' paired with sibling tools 'gemini_shell' and 'gemini_json' indicates this executes Gemini CLI commands.
Attacks that exploit this kind of access
run_gemini. It is categorised as a Execute tool in the Gemini CLI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gemini CLI MCP Server MCP server in PolicyLayer and add a rule for run_gemini: 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 Gemini CLI MCP Server. Nothing to install.
run_gemini 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 run_gemini 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 run_gemini. 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.
run_gemini is provided by the Gemini CLI MCP Server MCP server (wminson/gemini_mcp_server). 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 →