create_test · MCP Software Engineer MCP: Risk & Policy

WHAT IT DOES

What create_test does on MCP Software Engineer

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

WHY IT NEEDS A POLICY

Why create_test needs a policy

This tool creates new test files, which is a reversible write operation. Test files are development artifacts, not production data or executable code that runs against live systems. Creation can be undone by deletion. Severity is low because test files have minimal blast radius—misuse creates unnecessary files but doesn't delete data, corrupt systems, or execute arbitrary operations.

From the tool's definition Tool name 'create_test' and description 'Create test file for specific component/function' indicate file creation without modification of production systems or deletion of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_test Rate-limited

create_test 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": {
    "create_test": {
      "limits": [
        {
          "counter": "create_test_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 MCP Software Engineer, so you can run agents against it safely.

FAQ

Questions about create_test

What does the create_test tool do? +

Create test file for specific component/function. It is categorised as a Write tool in the MCP Software Engineer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_test? +

Register the MCP Software Engineer MCP server in PolicyLayer and add a rule for create_test: 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 MCP Software Engineer. Nothing to install.

What risk level is create_test? +

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

Can I rate-limit create_test? +

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

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

create_test is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.