run-view
Views a workflow run by ID. Returns structured data with status, conclusion, jobs (with steps), and workflow details.
This record as markdown: /tools/io-github-dave-london-cargo/run-view.md
What run-view does on Cargo
AI agents call run-view to retrieve information from Cargo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why run-view is rated Low
The tool only retrieves and displays information about a workflow run — status, conclusion, jobs, steps. No data is created, modified, or deleted. Pure read operation with minimal blast radius.
From the tool's definition Views a workflow run by ID. Returns structured data with status, conclusion, jobs (with steps), and workflow details.
Attacks that exploit this kind of access
The rule that runs run-view safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run-view, this is the rule to start with:
run-view is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cargo, apply this rule, and every run-view call is checked against it from then on.
Questions about run-view
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 Cargo MCP Server, which means it retrieves data without modifying state.
Register the Cargo 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 Cargo. 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 Cargo MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cargo, and thousands of servers like it.
This server
Across the catalogue