issue-update

Updates issue metadata (title, body, labels, assignees, milestone, projects).

SERVERCargo SOURCEDave-London/Pare
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about issue-update

What does the issue-update tool do? +

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.

How do I enforce a policy on issue-update? +

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.

What risk level is issue-update? +

issue-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit issue-update? +

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.

How do I block issue-update completely? +

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.

What MCP server provides issue-update? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cargo's. Pull the full record:

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.