List all recently issued human-made music certifications.
AI agents call vhc_registry to retrieve information from Verified Human 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 retrieves certification data from a registry. It performs a read-only operation that returns information about recently issued certifications. There is no capability to modify, delete, or execute operations—only to view existing data. The blast radius of misuse is minimal; an attacker could only enumerate certifications but cannot alter records or trigger external actions.
From the tool's definition Tool name 'vhc_registry' and description 'List all recently issued human-made music certifications' indicate retrieval of data without modification. The verb 'List' is a query operation that retrieves information from a registry with no side effects.
Attacks that exploit this kind of access
List all recently issued human-made music certifications. It is categorised as a Read tool in the Verified Human MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Verified Human MCP Server MCP server in PolicyLayer and add a rule for vhc_registry: 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 Verified Human MCP Server. Nothing to install.
vhc_registry 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 vhc_registry 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 vhc_registry. 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.
vhc_registry is provided by the Verified Human MCP Server MCP server (verifiedhumancert/verified-human-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →