github_link_repo · VibeServe MCP: Risk & Policy

WHAT IT DOES

What github_link_repo does on VibeServe

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

WHY IT NEEDS A POLICY

Why github_link_repo needs a policy

This tool creates a new linkage between VibeServe and an external GitHub repository, and may clone repository contents to the local system. This is a reversible write operation (the link can be removed, clones can be deleted). It does not execute arbitrary code from the repo, merely integrates it into scope.

From the tool's definition Tool description states 'Add a GitHub repo to VibeServe scope. Optionally clone it locally.' The verb 'Add' and the action of linking/cloning represent modification of the server's state and local filesystem.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_link_repo Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_link_repo": {
      "limits": [
        {
          "counter": "github_link_repo_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 VibeServe, so you can run agents against it safely.

FAQ

Questions about github_link_repo

What does the github_link_repo tool do? +

Add a GitHub repo to VibeServe scope. Optionally clone it locally. It is categorised as a Write tool in the VibeServe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_link_repo? +

Register the VibeServe MCP server in PolicyLayer and add a rule for github_link_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 VibeServe. Nothing to install.

What risk level is github_link_repo? +

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

Can I rate-limit github_link_repo? +

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

How do I block github_link_repo completely? +

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

What MCP server provides github_link_repo? +

github_link_repo is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.