# verify_credential

Verify a W3C Verifiable Credential — checks cryptographic signature, schema, and revocation status

Agent View of the PolicyLayer registry record for `verify_credential`. HTML page: https://policylayer.com/tools/81pass-mcp-server/verify-credential

## Facts

- Tool: `verify_credential`
- Server: 81pass (`@81pass/mcp-server`) — https://policylayer.com/tools/81pass-mcp-server.md
- Install: `npx -y @81pass/mcp-server`
- Homepage: https://www.npmjs.com/package/@81pass/mcp-server
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

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

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "verify_credential",
    "arguments": {
      "credential": "<credential>"
    }
  }
}
```

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

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 81pass:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_credential": {}
  }
}
```

## Other tools on 81pass (13)

- `revoke_credential` — Destructive — https://policylayer.com/tools/81pass-mcp-server/revoke-credential.md
- `check_credential_status` — Read — https://policylayer.com/tools/81pass-mcp-server/check-credential-status.md
- `get_billing_balance` — Read — https://policylayer.com/tools/81pass-mcp-server/get-billing-balance.md
- `get_endorsement_ledger` — Read — https://policylayer.com/tools/81pass-mcp-server/get-endorsement-ledger.md
- `batch_assign_pass_logistics` — Write — https://policylayer.com/tools/81pass-mcp-server/batch-assign-pass-logistics.md
- `batch_audit_and_heal_passes` — Write — https://policylayer.com/tools/81pass-mcp-server/batch-audit-and-heal-passes.md
- `issue_credential` — Write — https://policylayer.com/tools/81pass-mcp-server/issue-credential.md
- `manage_partner_offers` — Write — https://policylayer.com/tools/81pass-mcp-server/manage-partner-offers.md
- `request_endorsement` — Write — https://policylayer.com/tools/81pass-mcp-server/request-endorsement.md
- `resolve_did` — Write — https://policylayer.com/tools/81pass-mcp-server/resolve-did.md
- `suspend_credential` — Write — https://policylayer.com/tools/81pass-mcp-server/suspend-credential.md
- `topup_billing_wallet` — Write — https://policylayer.com/tools/81pass-mcp-server/topup-billing-wallet.md
- `undo_agent_action` — Write — https://policylayer.com/tools/81pass-mcp-server/undo-agent-action.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=81pass-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/81pass-mcp-server
