add_card_to_column · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_card_to_column does on GitHub MCP Server

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

The tool creates/adds new data (a card) to a project management system in a reversible manner. It does not execute code, delete data, move money, or trigger external operations. The scope is limited to GitHub project card management with minimal blast radius if misused—worst case being cluttered project boards that can be cleaned up. This is a straightforward Write operation.

From the tool's definition Tool name 'add_card_to_column' and description 'Add a new card to a project column' indicate creation of a new project management artifact. This is a write operation that creates a card (metadata/organizational object) within a GitHub project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_card_to_column Rate-limited

add_card_to_column 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_card_to_column": {
      "limits": [
        {
          "counter": "add_card_to_column_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_card_to_column

What does the add_card_to_column tool do? +

Add a new card to a project column. 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_card_to_column? +

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

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

Can I rate-limit add_card_to_column? +

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

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

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