Create a milestone in a repository
AI agents use create_milestone to create or update resources in Forgejo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
This tool creates a new milestone, which is a write operation that modifies repository state but is fully reversible. It does not execute code, delete data permanently, or involve financial transactions. The blast radius is low—a malicious milestone creation causes minimal harm and can be easily undone.
From the tool's definition Tool name 'create_milestone' and description 'Create a milestone in a repository' indicate data creation. Milestones are reversible metadata in version control (can be deleted/modified later).
Documented attack patterns abuse exactly the kind of access create_milestone gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for create_milestone:
{
"version": "1",
"default": "deny",
"tools": {
"create_milestone": {
"limits": [
{
"counter": "create_milestone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_milestone 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 milestone in a repository. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for create_milestone: 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 Forgejo. Nothing to install.
create_milestone 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_milestone 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_milestone. 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_milestone is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Forgejo, 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.
103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.