batch_link_to_project · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What batch_link_to_project does on GitHub MCP Server

AI agents use batch_link_to_project 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 batch_link_to_project needs a policy

The tool creates or modifies relationships between issues and projects—a reversible write operation. It affects multiple records in parallel (batch operation), which increases the blast radius if misapplied (e.g., linking many issues to the wrong project), but the action remains reversible (issues can be unlinked).

From the tool's definition batch_link_to_project links (associates) multiple issues to a GitHub Project board. This is a write operation that modifies the state of issues by creating associations with projects, but does not delete or irreversibly destroy data.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_link_to_project Rate-limited

batch_link_to_project 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": {
    "batch_link_to_project": {
      "limits": [
        {
          "counter": "batch_link_to_project_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 batch_link_to_project

What does the batch_link_to_project tool do? +

Link multiple issues to a GitHub Project (v2) board in parallel. 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 batch_link_to_project? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for batch_link_to_project: 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 batch_link_to_project? +

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

Can I rate-limit batch_link_to_project? +

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

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

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