Critical Risk →

copilot_remove_seats

Remove Copilot seats for specified users in an organization

How to control copilot_remove_seats ↓

AI agents call copilot_remove_seats to permanently remove resources in Sage MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Removing Copilot seats revokes access/licenses for specified users, which is an irreversible action (at least without re-provisioning). It has a significant blast radius as it can disrupt AI-assisted development workflows for multiple users across an organization. This is more than a Write operation because revoking access/entitlements is not easily reversible and constitutes destructive removal of permissions.

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

Documented attack patterns abuse exactly the kind of access copilot_remove_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_remove_seats:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "copilot_remove_seats"
  ]
}

copilot_remove_seats disappears from the agent's tool list entirely, and any attempt to call it is denied. 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the copilot_remove_seats tool do? +

Remove Copilot seats for specified users in an organization. It is categorised as a Destructive tool in the Sage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on copilot_remove_seats? +

Register the Sage MCP server in PolicyLayer and add a rule for copilot_remove_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_remove_seats? +

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

Can I rate-limit copilot_remove_seats? +

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

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

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