Critical Risk →

copilot_add_seats

Add Copilot seats for specified users in an organization

How to control copilot_add_seats ↓

AI agents use copilot_add_seats to commit financial operations through Sage MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Adding Copilot seats commits a financial obligation — GitHub Copilot is a paid subscription service, and provisioning seats directly incurs per-seat billing charges for the organization. This falls squarely in the Financial category as it creates a recurring cost commitment.

From the tool's definition Add Copilot seats for specified users in an organization

Documented attack patterns abuse exactly the kind of access copilot_add_seats gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for copilot_add_seats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "copilot_add_seats": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to copilot_add_seats is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Go deeper

What does the copilot_add_seats tool do? +

Add Copilot seats for specified users in an organization. It is categorised as a Financial tool in the Sage MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on copilot_add_seats? +

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

What risk level is copilot_add_seats? +

copilot_add_seats is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit copilot_add_seats? +

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

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

copilot_add_seats is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.