release-create
Creates a new GitHub release with optional asset uploads. Returns structured data with tag, URL, draft, prerelease status, and assets uploaded count.
This record as markdown: /tools/io-github-dave-london-cargo/release-create.md
What release-create does on Cargo
AI agents use release-create 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 release-create is rated Medium
This tool creates new GitHub releases and uploads assets, which are reversible write operations (releases can be deleted or modified afterward). It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could publish unintended releases to users, but the impact is limited to GitHub release management and can be undone.
From the tool's definition Tool description states it "Creates a new GitHub release" which is a create operation that modifies GitHub release data. Returns structured data including "tag, URL, draft, prerelease status, and assets uploaded count" confirming creation of release artifacts.
Attacks that exploit this kind of access
The rule that runs release-create 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 release-create, this is the rule to start with:
release-create 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 release-create call is checked against it from then on.
Questions about release-create
Creates a new GitHub release with optional asset uploads. Returns structured data with tag, URL, draft, prerelease status, and assets uploaded count. 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 release-create: 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.
release-create 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 release-create 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 release-create. 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.
release-create 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