AI agents call remove_list_member to permanently remove resources in X(Twitter) V2 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a member from a list is an irreversible deletion action (the membership is removed). The sibling tool 'add_list_member' confirms this is the inverse operation. While the description is empty (lowering confidence), the name clearly implies a destructive action. Severity is medium since it affects list membership but not core account data.
From the tool's definition Tool name 'remove_list_member' implies removing/deleting a member from a list; description is empty providing no additional context
Documented attack patterns abuse exactly the kind of access remove_list_member gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and X(Twitter) V2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_list_member:
{
"version": "1",
"default": "deny",
"hide": [
"remove_list_member"
]
}remove_list_member 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.
remove_list_member. It is categorised as a Destructive tool in the X(Twitter) V2 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the X(Twitter) V2 MCP Server MCP server in PolicyLayer and add a rule for remove_list_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 X(Twitter) V2 MCP Server. Nothing to install.
remove_list_member 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 remove_list_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.
Set action: deny in the PolicyLayer policy for remove_list_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.
remove_list_member is provided by the X(Twitter) V2 MCP Server MCP server (nexusx-mcp/x-v2-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from X(Twitter) V2 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.
16 X(Twitter) V2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.