AI agents use request_project_transfer 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.
Requesting a project transfer is a Write operation as it creates a transfer request that can potentially be reversed or cancelled before completion. However, it has high severity because if accepted, it changes ownership of a project, potentially losing access to it. The 'request' nature implies it's not immediately destructive but sets in motion a significant ownership change.
From the tool's definition "Request project transfer" - initiates a transfer of project ownership
Documented attack patterns abuse exactly the kind of access request_project_transfer 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 request_project_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"request_project_transfer": {
"limits": [
{
"counter": "request_project_transfer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}request_project_transfer 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.
Request project transfer. 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 request_project_transfer: 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.
request_project_transfer 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 request_project_transfer 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 request_project_transfer. 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.
request_project_transfer 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.