AI agents call deleteOneWorkspaceMember to permanently remove resources in Twenty MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of workspace members is an irreversible action that cannot be undone without administrative intervention or backups. It destroys data and access permissions, making it Destructive rather than Write. In a CRM context, removing team members from a workspace can disrupt operations, collaboration, and audit trails.
From the tool's definition Tool name is 'deleteOneWorkspaceMember' with description 'Delete One workspaceMember'. The verb 'Delete' combined with 'One' indicates removal of a specific workspace member record.
Documented attack patterns abuse exactly the kind of access deleteOneWorkspaceMember gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteOneWorkspaceMember:
{
"version": "1",
"default": "deny",
"hide": [
"deleteOneWorkspaceMember"
]
}deleteOneWorkspaceMember disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete One workspaceMember. It is categorised as a Destructive tool in the Twenty MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for deleteOneWorkspaceMember: 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 Twenty MCP Server. Nothing to install.
deleteOneWorkspaceMember 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 deleteOneWorkspaceMember 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 deleteOneWorkspaceMember. 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.
deleteOneWorkspaceMember is provided by the Twenty MCP Server MCP server (jdu278/twenty-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twenty MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
219 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.