cursor_remove_member

Remove a member from the Cursor team by user ID

SERVERSage MCP SOURCEsagemcp/sagemcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/cursor-remove-member.md

WHAT IT DOES

What cursor_remove_member does on Sage MCP

AI agents call cursor_remove_member 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.

RISK

Why cursor_remove_member is rated Critical

Removing a team member is an irreversible action that cannot be undone without manual intervention from an administrator. This represents permanent deletion/modification of organizational access and cannot be reversed through any automated recovery mechanism, classifying it as Destructive.

From the tool's definition Tool name includes 'remove_member' and description states 'Remove a member from the Cursor team by user ID'. The term 'remove' combined with targeting a specific user indicates irreversible membership revocation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cursor_remove_member 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 cursor_remove_member, this is the rule to start with:

cursor_remove_member Hidden

cursor_remove_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cursor_remove_member"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about cursor_remove_member

What does the cursor_remove_member tool do? +

Remove a member from the Cursor team by user ID. 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 cursor_remove_member? +

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

cursor_remove_member 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 cursor_remove_member? +

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

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

cursor_remove_member 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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →