remove_members_from_team

Removes users from team membership, revoking their access to team-owned records and team-based permissions. Use this when users no longer need team access or are changing roles.

Server Dataverse MCP Server wizspdemo/dataverse-mcp2
Category Destructive
Risk class Critical
Parameters 00 required

What remove_members_from_team does on Dataverse MCP Server

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

Why remove_members_from_team needs a policy

Removing team membership revokes access rights and permissions in a way that is not trivially reversible (requires re-adding users and reconfiguring permissions). The blast radius is high as it can lock users out of team-owned records and remove security privileges, potentially disrupting business operations.

From the tool's definition Removes users from team membership, revoking their access to team-owned records and team-based permissions

Questions about remove_members_from_team

What does the remove_members_from_team tool do? +

Removes users from team membership, revoking their access to team-owned records and team-based permissions. Use this when users no longer need team access or are changing roles. It is categorised as a Destructive tool in the Dataverse MCP Server 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 remove_members_from_team? +

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

What risk level is remove_members_from_team? +

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

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

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

remove_members_from_team is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.