set_repo_collaborator_permission · Ghe Mcp Gateway MCP

WHAT IT DOES

What set_repo_collaborator_permission does on Ghe Mcp Gateway

AI agents use set_repo_collaborator_permission to create or update resources in Ghe Mcp Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghe Mcp Gateway environment.

WHY IT NEEDS A POLICY

Why set_repo_collaborator_permission needs a policy

This tool modifies access control permissions by adding or updating collaborator roles on repositories. While reversible (permissions can be changed again), this is a sensitive operation that affects repository security posture and who can access code/data.

From the tool's definition Tool description explicitly states 'Add or update a collaborator's permission on a repo' and marks it as 'WRITE OPERATION'. The verb phrases 'Add or update' confirm reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_repo_collaborator_permission Rate-limited

set_repo_collaborator_permission 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_repo_collaborator_permission": {
      "limits": [
        {
          "counter": "set_repo_collaborator_permission_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ghe Mcp Gateway, so you can run agents against it safely.

FAQ

Questions about set_repo_collaborator_permission

What does the set_repo_collaborator_permission tool do? +

Add or update a collaborator's permission on a repo. WRITE OPERATION. It is categorised as a Write tool in the Ghe Mcp Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_repo_collaborator_permission? +

Register the Ghe Mcp Gateway MCP server in PolicyLayer and add a rule for set_repo_collaborator_permission: 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 Ghe Mcp Gateway. Nothing to install.

What risk level is set_repo_collaborator_permission? +

set_repo_collaborator_permission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_repo_collaborator_permission? +

Yes. Add a rate_limit block to the set_repo_collaborator_permission 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.

How do I block set_repo_collaborator_permission completely? +

Set action: deny in the PolicyLayer policy for set_repo_collaborator_permission. 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.

What MCP server provides set_repo_collaborator_permission? +

set_repo_collaborator_permission is provided by the Ghe Mcp Gateway MCP server (mholzinger/ghe-mcp-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.