Creates a new GitHub release with optional asset uploads. Returns structured data with tag, URL, draft, prerelease status, and assets uploaded count.
AI agents use release-create to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
Creating a GitHub release is a write operation that publishes software releases publicly. While reversible (releases can be deleted), the act of creating and publishing a release with assets can have significant downstream effects (users downloading, CI/CD pipelines triggering). The 'asset uploads' component adds to the blast radius.
From the tool's definition Creates a new GitHub release with optional asset uploads
Documented attack patterns abuse exactly the kind of access release-create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for release-create:
{
"version": "1",
"default": "deny",
"tools": {
"release-create": {
"limits": [
{
"counter": "release-create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make 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 Make. 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 Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.