AI agents use create_release to create or update resources in Bugsink MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bugsink MCP Server environment.
This tool creates a new release record in the error tracking system, which is a reversible write operation. It does not execute code, delete data permanently, or involve financial transactions. However, it has medium severity because creating releases can affect deployment workflows, triggering downstream automation or affecting system visibility to teams.
From the tool's definition Tool is named 'create_release' with description 'Create a new release for a project', indicating creation of a new data entity (release record) that can be modified or deleted later.
Documented attack patterns abuse exactly the kind of access create_release gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bugsink MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_release:
{
"version": "1",
"default": "deny",
"tools": {
"create_release": {
"limits": [
{
"counter": "create_release_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_release 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.
Create a new release for a project. It is categorised as a Write tool in the Bugsink MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bugsink MCP Server MCP server in PolicyLayer and add a rule for create_release: 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 Bugsink MCP Server. Nothing to install.
create_release 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 create_release 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 create_release. 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.
create_release is provided by the Bugsink MCP Server MCP server (j-shelfwood/bugsink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bugsink MCP Server, 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.
16 Bugsink MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.