issue-view
Views an issue by number or URL. Returns structured data with state, labels, assignees, author, milestone, close reason, and body.
This record as markdown: /tools/io-github-dave-london-cargo/issue-view.md
What issue-view does on Cargo
AI agents call issue-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 issue-view is rated Low
This tool only retrieves and returns issue data. It has no side effects, does not modify any data, and is purely a read/query operation.
From the tool's definition Views an issue by number or URL. Returns structured data with state, labels, assignees, author, milestone, close reason, and body.
Attacks that exploit this kind of access
The rule that runs issue-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 issue-view, this is the rule to start with:
issue-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 issue-view call is checked against it from then on.
Questions about issue-view
Views an issue by number or URL. Returns structured data with state, labels, assignees, author, milestone, close reason, and body. 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 issue-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.
issue-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 issue-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 issue-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.
issue-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