Get project domain by project id/name and domain name
AI agents call get_project_domain to retrieve information from Vercel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns domain information associated with a project without modifying any state. It is a straightforward data retrieval operation with no side effects, falling clearly into the Read category. The severity is low because retrieving domain configuration details poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name and description indicate retrieval: 'get_project_domain' performs a 'Get' operation to retrieve domain information by project id/name and domain name. No modification, deletion, or execution of code is implied.
Documented attack patterns abuse exactly the kind of access get_project_domain 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 get_project_domain:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_domain": {}
}
}get_project_domain is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get project domain by project id/name and domain name. It is categorised as a Read tool in the Vercel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for get_project_domain: 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.
get_project_domain is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_project_domain 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 get_project_domain. 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.
get_project_domain 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.