Remove a member from a specific project
AI agents call remove_project_member to permanently remove resources in Vercel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a project member is a destructive, hard-to-reverse action. While technically a deletion of a membership record rather than data, it revokes access permissions and typically cannot be undone without re-inviting the member. The blast radius is high because it can cut off a collaborator's access to a production project immediately.
From the tool's definition 'Remove a member from a specific project' — removing membership is an irreversible access-control action that revokes a user's project access
Documented attack patterns abuse exactly the kind of access remove_project_member gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vercel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_project_member:
{
"version": "1",
"default": "deny",
"hide": [
"remove_project_member"
]
}remove_project_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 a member from a specific project. It is categorised as a Destructive tool in the Vercel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for remove_project_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 Vercel MCP Server. Nothing to install.
remove_project_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_project_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_project_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_project_member is provided by the Vercel MCP Server MCP server (quegenx/vercel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 154 Vercel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
154 Vercel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.