update_test_run

Update a test run

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-test-run.md

WHAT IT DOES

What update_test_run does on Huly

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

RISK

Why update_test_run is rated Medium

The tool updates (modifies) a test run object, which is a reversible write operation. Without evidence of deletion, irreversibility, code execution, or financial impact, this falls under Write category. Severity is medium because modifying test run data could affect test reporting and CI/CD workflows, but the impact is typically scoped to a single test entity and is reversible.

From the tool's definition Tool name is 'update_test_run' and description states 'Update a test run', which modifies existing data in the Huly system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_test_run 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 update_test_run, this is the rule to start with:

update_test_run Rate-limited

update_test_run 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": {
    "update_test_run": {
      "limits": [
        {
          "counter": "update_test_run_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_test_run

What does the update_test_run tool do? +

Update a test run. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_test_run? +

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

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

Can I rate-limit update_test_run? +

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

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

update_test_run is provided by the Huly MCP server (@firfi/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 518 Huly tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →