Low Risk

list_edge_configs

List all Edge Configs

How to control list_edge_configs ↓

AI agents call list_edge_configs 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.

Low Risk

This tool performs a read-only operation that queries and returns Edge Configs without creating, modifying, deleting, or executing any operations. The 'list' action is explicitly a Read category operation with minimal security risk unless the configs themselves contain highly sensitive information, but the tool itself poses no inherent danger.

From the tool's definition Tool name 'list_edge_configs' and description 'List all Edge Configs' indicate a retrieval/query operation with no modification of data.

Documented attack patterns abuse exactly the kind of access list_edge_configs 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 list_edge_configs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_edge_configs": {}
  }
}

list_edge_configs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Vercel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_edge_configs tool do? +

List all Edge Configs. It is categorised as a Read tool in the Vercel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_edge_configs? +

Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for list_edge_configs: 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.

What risk level is list_edge_configs? +

list_edge_configs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_edge_configs? +

Yes. Add a rate_limit block to the list_edge_configs 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.

How do I block list_edge_configs completely? +

Set action: deny in the PolicyLayer policy for list_edge_configs. 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.

What MCP server provides list_edge_configs? +

list_edge_configs 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.

Enforce policy on every Vercel MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.