get_run

Fetch the full metadata of a single test run.

Server Testrail sergey-bl/testrail-mcp
Category Read
Risk class Low
Parameters 00 required

What get_run does on Testrail

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

Why get_run needs a policy

This tool retrieves and queries data about a test run without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name is 'get_run' and description states 'Fetch the full metadata of a single test run' — the verb 'fetch' and passive retrieval of metadata indicate a read-only operation with no side effects.

Questions about get_run

What does the get_run tool do? +

Fetch the full metadata of a single test run. It is categorised as a Read tool in the Testrail MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_run? +

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

What risk level is get_run? +

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

Can I rate-limit get_run? +

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

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

get_run is provided by the Testrail MCP server (sergey-bl/testrail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

get_run is one line of Testrail's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.