AI agents use generate-tests to create or update resources in VibeCoding System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VibeCoding System environment.
This tool creates new test cases and test files. While test generation is a constructive action that modifies the codebase by adding new content, these modifications are reversible (tests can be deleted or updated). It does not execute code against production systems, delete data, or trigger external operations. It falls under Write category—it creates new development artifacts that can be modified or removed.
From the tool's definition Tool description: 'Generate test cases for existing code'. Creates new test files/cases which are reversible modifications to the codebase.
Documented attack patterns abuse exactly the kind of access generate-tests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VibeCoding System, and nothing reaches the server without passing your rules. This is the rule we recommend for generate-tests:
{
"version": "1",
"default": "deny",
"tools": {
"generate-tests": {
"limits": [
{
"counter": "generate-tests_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Generate test cases for existing code. It is categorised as a Write tool in the VibeCoding System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VibeCoding System 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 VibeCoding System. Nothing to install.
generate-tests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
generate-tests is provided by the VibeCoding System MCP server (zenobia000/vibecoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VibeCoding System, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 VibeCoding System tools catalogued and risk-classified — across an index of 43,000+ MCP servers.