generate_unit_tests · Gemini Agent MCP Server MCP

WHAT IT DOES

What generate_unit_tests does on Gemini Agent MCP Server

AI agents use generate_unit_tests to create or update resources in Gemini Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gemini Agent MCP Server environment.

WHY IT NEEDS A POLICY

Why generate_unit_tests needs a policy

This tool creates new test files or appends test code to existing files, which is a reversible write operation. It does not execute code, delete data, or interact with financial systems. The severity is low because generated unit tests are development artifacts that can be easily modified or deleted, with no destructive consequences or side effects on production systems.

From the tool's definition The tool description states it 'Generates unit tests for a given function or class in a file.' The word 'Generates' indicates creation of new content (test code) within the filesystem.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_unit_tests Rate-limited

generate_unit_tests stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_unit_tests": {
      "limits": [
        {
          "counter": "generate_unit_tests_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Agent MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_unit_tests

What does the generate_unit_tests tool do? +

Generates unit tests for a given function or class in a file. It is categorised as a Write tool in the Gemini Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_unit_tests? +

Register the Gemini Agent MCP Server MCP server in PolicyLayer and add a rule for generate_unit_tests: 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 Agent MCP Server. Nothing to install.

What risk level is generate_unit_tests? +

generate_unit_tests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_unit_tests? +

Yes. Add a rate_limit block to the generate_unit_tests 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 generate_unit_tests completely? +

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

generate_unit_tests is provided by the Gemini Agent MCP Server MCP server (leesinliang/geminicliagentmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.