Set the topics for a repository (replaces all existing topics)
AI agents use update_repo_topics 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 or modifies data (repository topics) without permanently deleting anything. The operation is reversible since topics can be updated again to different values or cleared. While it affects repository metadata and could be misused to alter repo discoverability, it does not delete data irreversibly, execute arbitrary code, or involve financial transactions.
From the tool's definition Set the topics for a repository (replaces all existing topics) — modifies repository metadata by replacing existing topics, a reversible write operation.
Documented attack patterns abuse exactly the kind of access update_repo_topics 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 update_repo_topics:
{
"version": "1",
"default": "deny",
"tools": {
"update_repo_topics": {
"limits": [
{
"counter": "update_repo_topics_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_repo_topics 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.
Set the topics for a repository (replaces all existing topics). 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 update_repo_topics: 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.
update_repo_topics 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 update_repo_topics 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 update_repo_topics. 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.
update_repo_topics 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.