Views a workflow run by ID. Returns structured data with status, conclusion, jobs (with steps), and workflow details.
AI agents call run-view to retrieve information from Test without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves and returns information about a workflow run. There are no side effects, modifications, or executions involved — it is a pure read/query operation.
From the tool's definition Views a workflow run by ID. Returns structured data with status, conclusion, jobs (with steps), and workflow details.
Documented attack patterns abuse exactly the kind of access run-view gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Test, and nothing reaches the server without passing your rules. This is the rule we recommend for run-view:
{
"version": "1",
"default": "deny",
"tools": {
"run-view": {}
}
} run-view is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Views a workflow run by ID. Returns structured data with status, conclusion, jobs (with steps), and workflow details. It is categorised as a Read tool in the Test MCP Server, which means it retrieves data without modifying state.
Register the Test MCP server in PolicyLayer and add a rule for run-view: 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 Test. Nothing to install.
run-view is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the run-view 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.
Set action: deny in the PolicyLayer policy for run-view. 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.
run-view is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Test, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Test tools catalogued and risk-classified — across an index of 43,000+ MCP servers.