add_collaborator · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_collaborator does on GitHub MCP Server

AI agents use add_collaborator to create or update resources in GitHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.

WHY IT NEEDS A POLICY

Why add_collaborator needs a policy

Adding a collaborator modifies repository access control and permissions, which is a reversible write operation. This is categorized as Write rather than Execute because it directly modifies data (access permissions) rather than triggering external operations. Severity is high because granting unintended collaborator access could expose sensitive code or allow unauthorized modifications.

From the tool's definition Tool name 'add_collaborator' indicates modification of repository access permissions. No description provided, but the name clearly indicates a write operation that changes repository state by adding access permissions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_collaborator Rate-limited

add_collaborator 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": {
    "add_collaborator": {
      "limits": [
        {
          "counter": "add_collaborator_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 GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about add_collaborator

What does the add_collaborator tool do? +

add_collaborator. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_collaborator? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for add_collaborator: 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 GitHub MCP Server. Nothing to install.

What risk level is add_collaborator? +

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

Can I rate-limit add_collaborator? +

Yes. Add a rate_limit block to the add_collaborator 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 add_collaborator completely? +

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

add_collaborator is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.