setup_testing · MCP Software Engineer MCP: Risk & Policy

WHAT IT DOES

What setup_testing does on MCP Software Engineer

AI agents use setup_testing 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 setup_testing needs a policy

This tool creates or modifies testing framework configurations and files as part of the development workflow. These changes are reversible (files can be edited, deleted, or reconfigured), so it falls under Write rather than Execute. While it may trigger some framework initialization, the primary action is setting up configuration, not running arbitrary code or external processes.

From the tool's definition Tool name 'setup_testing' and description 'Setup testing framework and configuration' indicate creation and modification of testing infrastructure and configuration files, which are reversible operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_testing Rate-limited

setup_testing 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": {
    "setup_testing": {
      "limits": [
        {
          "counter": "setup_testing_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 setup_testing

What does the setup_testing tool do? +

Setup testing framework and configuration. 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 setup_testing? +

Register the MCP Software Engineer MCP server in PolicyLayer and add a rule for setup_testing: 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 setup_testing? +

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

Can I rate-limit setup_testing? +

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

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

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