This record as markdown: /tools/sqcows-forgejo-mcp/edit-org.md
What edit_org does on Forgejo
AI agents use edit_org 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.
Why edit_org is rated Medium
This tool creates or modifies organizational configuration/metadata reversibly without permanently deleting data or executing arbitrary code. In a Forgejo/Gitea context, editing an organization could affect permissions, settings, and visibility for many repositories and users, warranting 'high' severity due to blast radius, but it is reversible and thus Write not Destructive.
From the tool's definition Tool name 'edit_org' and description 'Edit an organization' indicate modification of organizational data/settings.
Attacks that exploit this kind of access
The rule that runs edit_org safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edit_org, this is the rule to start with:
edit_org 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every edit_org call is checked against it from then on.
Questions about edit_org
Edit an organization. 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 edit_org: 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.
edit_org 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 edit_org 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 edit_org. 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.
edit_org 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.
More on Forgejo, and thousands of servers like it.
This server
Across the catalogue