verify_credential
Verify a W3C Verifiable Credential — checks cryptographic signature, schema, and revocation status
This record as markdown: /tools/81pass-mcp-server/verify-credential.md
What verify_credential does on 81pass
AI agents call verify_credential to retrieve information from 81pass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
credential | string | Yes | The full W3C Verifiable Credential as JSON string or ID |
Parameters from the server's own tool schema.
Why verify_credential is rated Low
Even though verify_credential only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs verify_credential safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 81pass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_credential, this is the rule to start with:
verify_credential is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 81pass, apply this rule, and every verify_credential call is checked against it from then on.
Questions about verify_credential
Verify a W3C Verifiable Credential — checks cryptographic signature, schema, and revocation status. It is categorised as a Read tool in the 81pass MCP Server, which means it retrieves data without modifying state.
verify_credential accepts 1 parameter: credential. Required: credential. The full parameter table on this page comes from the server's own tool schema.
Register the 81pass MCP server in PolicyLayer and add a rule for verify_credential: 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 81pass. Nothing to install.
verify_credential 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 verify_credential 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 verify_credential. 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.
verify_credential is provided by the 81pass MCP server (@81pass/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 81pass, and thousands of servers like it.
This server
Across the catalogue