Check that a cache artifact with the given hash exists
AI agents call check_artifact 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 performs a read-only check operation to verify the existence of a cache artifact. It queries state without creating, modifying, deleting, or executing any side effects. The verb 'check' combined with 'exists' indicates a simple lookup/verification operation typical of Read category tools.
From the tool's definition Tool name 'check_artifact' with description 'Check that a cache artifact with the given hash exists' indicates a query/verification operation that retrieves status information without modification.
Documented attack patterns abuse exactly the kind of access check_artifact 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 check_artifact:
{
"version": "1",
"default": "deny",
"tools": {
"check_artifact": {}
}
}check_artifact 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.
Check that a cache artifact with the given hash exists. 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 check_artifact: 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.
check_artifact 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 check_artifact 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 check_artifact. 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.
check_artifact 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.