gemini_with_context · Gemini CLI MCP Server MCP

WHAT IT DOES

What gemini_with_context does on Gemini CLI MCP Server

AI agents invoke gemini_with_context 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.

WHY IT NEEDS A POLICY

Why gemini_with_context needs a policy

The description is empty, so classification relies on the tool name and server context. The sibling tools include shell execution (gemini_shell), session management, and prompt execution (run_gemini), suggesting this tool likely executes Gemini CLI prompts with some additional context.

From the tool's definition Tool name 'gemini_with_context' on a server that 'wraps the Gemini CLI to provide tools for executing prompts, managing chat sessions, and accessing CLI extensions'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gemini_with_context Rate-limited

gemini_with_context stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gemini_with_context": {
      "limits": [
        {
          "counter": "gemini_with_context_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gemini CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about gemini_with_context

What does the gemini_with_context tool do? +

gemini_with_context. 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.

How do I enforce a policy on gemini_with_context? +

Register the Gemini CLI MCP Server MCP server in PolicyLayer and add a rule for gemini_with_context: 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.

What risk level is gemini_with_context? +

gemini_with_context is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gemini_with_context? +

Yes. Add a rate_limit block to the gemini_with_context 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.

How do I block gemini_with_context completely? +

Set action: deny in the PolicyLayer policy for gemini_with_context. 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.

What MCP server provides gemini_with_context? +

gemini_with_context 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.