AI agents use add_project_member to create or update resources in Vercel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vercel MCP Server environment.
This tool creates a new project membership record. While it modifies access control state, the action is reversible (the member can be removed), making it a Write operation rather than Execute or Destructive.
From the tool's definition Tool name 'add_project_member' and description 'Adds a new member to a project' indicate creation of a new team/project association, which is a reversible data modification operation.
Documented attack patterns abuse exactly the kind of access add_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 add_project_member:
{
"version": "1",
"default": "deny",
"tools": {
"add_project_member": {
"limits": [
{
"counter": "add_project_member_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_project_member stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Adds a new member to a project. It is categorised as a Write tool in the Vercel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_project_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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.