run_task · GPA Backend Test Analyst MCP: Risk & Policy

WHAT IT DOES

What run_task does on GPA Backend Test Analyst MCP

AI agents invoke run_task to trigger actions in GPA Backend Test Analyst MCP. 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 run_task needs a policy

run_task triggers backend operations that can modify system state (generate_tests creates new test artifacts, generate_docs produces documentation files, full_analysis performs comprehensive backend analysis). While not destructive by design, the tool executes arbitrary backend processes whose actual impact depends on runtime parameters, making it Execute rather than Write.

From the tool's definition Tool description states it 'Executa task específica' (executes specific task) with explicit capabilities including analyze_coverage, generate_tests, diagnose_failure, generate_docs, and full_analysis.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_task Rate-limited

run_task 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": {
    "run_task": {
      "limits": [
        {
          "counter": "run_task_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 GPA Backend Test Analyst MCP, so you can run agents against it safely.

FAQ

Questions about run_task

What does the run_task tool do? +

v4.0 — Executa task específica: analyze_coverage, generate_tests, diagnose_failure, generate_docs, full_analysis. It is categorised as a Execute tool in the GPA Backend Test Analyst MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_task? +

Register the GPA Backend Test Analyst MCP server in PolicyLayer and add a rule for run_task: 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 GPA Backend Test Analyst MCP. Nothing to install.

What risk level is run_task? +

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

Can I rate-limit run_task? +

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

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

run_task is provided by the GPA Backend Test Analyst MCP server (renanpires-tech/mcpautomation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.