run_test_plan

Execute a test plan: creates a test run and one test result per plan item. Returns the run ID and count of results created. Optionally name the run and set a due date.

SERVERHuly SOURCEdugynoo/huly-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/run-test-plan.md

WHAT IT DOES

What run_test_plan does on Huly

AI agents invoke run_test_plan to trigger actions in Huly. 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.

RISK

Why run_test_plan is rated High

This tool executes test plans, which runs code or automated testing operations with side effects that depend on which test plan is selected and how it's configured. While not destructive (results are reversible), it triggers external test execution operations, making it Execute rather than Write.

From the tool's definition Tool description states it 'Execute[s] a test plan' and 'creates a test run and one test result per plan item', triggering external operations (test execution) whose effects depend on arguments (plan selection, optional run naming, due date setting).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_test_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_test_plan, this is the rule to start with:

run_test_plan Rate-limited

run_test_plan 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_test_plan": {
      "limits": [
        {
          "counter": "run_test_plan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every run_test_plan call is checked against it from then on.

FAQ

Questions about run_test_plan

What does the run_test_plan tool do? +

Execute a test plan: creates a test run and one test result per plan item. Returns the run ID and count of results created. Optionally name the run and set a due date. It is categorised as a Execute tool in the Huly 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_test_plan? +

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

What risk level is run_test_plan? +

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

Can I rate-limit run_test_plan? +

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

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

run_test_plan is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server →team_manager_approve_plan on Team Manager MCP →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →