removeListsMemberByUserId
Remove a user from a list membership.
This record as markdown: /tools/xdevplatform-xmcp/removelistsmemberbyuserid.md
What removeListsMemberByUserId does on Xdevplatform/xmcp
AI agents call removeListsMemberByUserId to permanently remove resources in Xdevplatform/xmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why removeListsMemberByUserId is rated Critical
Removing a user from a list membership is an irreversible deletion of that membership relationship. While the user still exists and could theoretically be re-added, the act of removal is a destructive operation that eliminates existing data (the membership record). The blast radius is medium as it affects list membership for potentially many users if misused.
From the tool's definition Remove a user from a list membership
Attacks that exploit this kind of access
The rule that runs removeListsMemberByUserId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For removeListsMemberByUserId, this is the rule to start with:
removeListsMemberByUserId is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Xdevplatform/xmcp, apply this rule, and every removeListsMemberByUserId call is checked against it from then on.
Questions about removeListsMemberByUserId
Remove a user from a list membership. It is categorised as a Destructive tool in the Xdevplatform/xmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for removeListsMemberByUserId: 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 Xdevplatform/xmcp. Nothing to install.
removeListsMemberByUserId is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the removeListsMemberByUserId 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.
Set action: deny in the PolicyLayer policy for removeListsMemberByUserId. 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.
removeListsMemberByUserId is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Xdevplatform/x, and thousands of servers like it.
Across the catalogue