AI agents use update_secret_name 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.
The tool modifies existing secret configuration by renaming it, which is a write operation. It is not destructive (the secret itself is not deleted, only renamed), not read-only (it changes state), and not execution of arbitrary code. The severity is medium because secrets are security-sensitive, but renaming is reversible and lower-risk than exposing, deleting, or rotating the actual secret value.
From the tool's definition Tool name 'update_secret_name' and description 'Change the name of a secret' indicate modification of an existing secret configuration. This is a reversible write operation that changes metadata (the name) of a stored secret.
Documented attack patterns abuse exactly the kind of access update_secret_name 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 update_secret_name:
{
"version": "1",
"default": "deny",
"tools": {
"update_secret_name": {
"limits": [
{
"counter": "update_secret_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_secret_name 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.
Change the name of a secret. 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 update_secret_name: 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.
update_secret_name 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 update_secret_name 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 update_secret_name. 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.
update_secret_name 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.