full_phase2_pipeline · Local Testing Agent MCP Server MCP

WHAT IT DOES

What full_phase2_pipeline does on Local Testing Agent MCP Server

AI agents invoke full_phase2_pipeline to trigger actions in Local Testing Agent MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why full_phase2_pipeline needs a policy

This tool executes an automated testing pipeline across a repository. While test execution is generally safe and reversible (tests don't modify production data), it triggers external code execution whose side effects depend on what tests do and what the repository contains. Misuse could exhaust resources, trigger unintended side effects in test environments, or expose secrets in test logs.

From the tool's definition Tool name 'full_phase2_pipeline' combined with server's stated capability to 'execute tests' and the presence of sibling tools like 'run_all_tests' and 'run_all_tests_parallel' indicates this triggers automated test execution workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

full_phase2_pipeline Rate-limited

full_phase2_pipeline stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "full_phase2_pipeline": {
      "limits": [
        {
          "counter": "full_phase2_pipeline_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Local Testing Agent MCP Server, so you can run agents against it safely.

FAQ

Questions about full_phase2_pipeline

What does the full_phase2_pipeline tool do? +

Convenience tool:. It is categorised as a Execute tool in the Local Testing Agent MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on full_phase2_pipeline? +

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

What risk level is full_phase2_pipeline? +

full_phase2_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit full_phase2_pipeline? +

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

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

full_phase2_pipeline is provided by the Local Testing Agent MCP Server MCP server (marcelkurvers/local-testing-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.