issue-update
Updates issue metadata (title, body, labels, assignees, milestone, projects).
This record as markdown: /tools/io-github-dave-london-cargo/issue-update.md
What issue-update does on Cargo
AI agents use issue-update to create or update resources in Cargo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cargo environment.
Why issue-update is rated Medium
The tool creates or modifies data reversibly: updating issue metadata such as title, body, labels, assignees, milestone, and projects are all changes that can be undone or corrected. This is characteristic of Write operations. Severity is medium because misuse could spam or corrupt issue tracking systems, but the changes are reversible and typically confined to one project's metadata.
From the tool's definition Tool description explicitly states it 'Updates issue metadata (title, body, labels, assignees, milestone, projects)' — this modifies data in an issue tracking system.
Attacks that exploit this kind of access
The rule that runs issue-update 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-update, this is the rule to start with:
issue-update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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-update call is checked against it from then on.
Questions about issue-update
Updates issue metadata (title, body, labels, assignees, milestone, projects). It is categorised as a Write tool in the Cargo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cargo MCP server in PolicyLayer and add a rule for issue-update: 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-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the issue-update 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-update. 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-update 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