get_test_run

Get test run details including all results. Accepts run ID or name within a project.

SERVERHuly SOURCEdugynoo/huly-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_test_run does on Huly

AI agents call get_test_run to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_test_run is rated Low

This tool retrieves and queries test run information without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The blast radius of misuse is minimal since it only exposes existing test data without creating, modifying, or deleting anything.

From the tool's definition Tool description states 'Get test run details including all results' — uses 'Get' which indicates data retrieval. Accepts run ID or name as parameters (query parameters), returns test run details and results without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_test_run Allowed

get_test_run is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_test_run": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_test_run

What does the get_test_run tool do? +

Get test run details including all results. Accepts run ID or name within a project. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_test_run? +

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

get_test_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_test_run? +

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

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

get_test_run 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →