Unstar a repository for the authenticated user
AI agents use unstar_repo 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.
Unstarring a repository modifies the user's starred repositories list. This is a reversible action (the user can re-star the repository), so it falls under Write rather than Destructive. The blast radius is low as it only affects the authenticated user's star list with no impact on the repository itself or other users.
From the tool's definition Unstar a repository for the authenticated user
Documented attack patterns abuse exactly the kind of access unstar_repo 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 unstar_repo:
{
"version": "1",
"default": "deny",
"tools": {
"unstar_repo": {
"limits": [
{
"counter": "unstar_repo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unstar_repo 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.
Unstar a repository for the authenticated user. 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 unstar_repo: 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.
unstar_repo 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 unstar_repo 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 unstar_repo. 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.
unstar_repo 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.