generate_tests · AutoDev MCP: Risk & Policy

WHAT IT DOES

What generate_tests does on AutoDev MCP

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

WHY IT NEEDS A POLICY

Why generate_tests needs a policy

This tool creates test artifacts (reversible data generation for testing), fitting the Write category. It logs requests for future processing rather than executing arbitrary code or deleting data. The 'stub' nature and logging mechanism suggest side effects that modify persistent state (SQLite logging mentioned in server description), making it Write rather than Read.

From the tool's definition Tool name 'generate_tests' and context of 'test generation' and 'logging request' indicates creating test artifacts. Server description mentions 'test pipelines' and 'evidence-based requirement generation' suggesting test creation workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_tests Rate-limited

generate_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_tests": {
      "limits": [
        {
          "counter": "generate_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 AutoDev MCP, so you can run agents against it safely.

FAQ

Questions about generate_tests

What does the generate_tests tool do? +

Stub for test generation (logs request for future extension). It is categorised as a Write tool in the AutoDev MCP 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_tests? +

Register the AutoDev MCP server in PolicyLayer and add a rule for generate_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 AutoDev MCP. Nothing to install.

What risk level is generate_tests? +

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

Can I rate-limit generate_tests? +

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

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

generate_tests is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.