copilot_add_seats

Add Copilot seats for specified users in an organization

SERVERSage MCP SOURCEsagemcp/sagemcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/copilot-add-seats.md

WHAT IT DOES

What copilot_add_seats does on Sage MCP

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.

RISK

Why copilot_add_seats is rated Critical

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copilot_add_seats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copilot_add_seats, this is the rule to start with:

copilot_add_seats Approval-gated

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

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every copilot_add_seats call is checked against it from then on.

FAQ

Questions about copilot_add_seats

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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →