revoke_credential
Revoke an existing credential in the Bitstring Status List. REQUIRES HUMAN CONFIRMATION.
This record as markdown: /tools/81pass-mcp-server/revoke-credential.md
What revoke_credential does on 81pass
AI agents call revoke_credential to permanently remove resources in 81pass, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Reason for revocation |
credentialId | string | Yes | The unique ID or URI of the credential to revoke |
confirmationToken | string | — | Confirmation token from step 1 |
Parameters from the server's own tool schema.
Why revoke_credential is rated Critical
An AI agent that decides to call revoke_credential doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 81pass is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs revoke_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 revoke_credential, this is the rule to start with:
revoke_credential is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 81pass, apply this rule, and every revoke_credential call is checked against it from then on.
Questions about revoke_credential
Revoke an existing credential in the Bitstring Status List. REQUIRES HUMAN CONFIRMATION. It is categorised as a Destructive tool in the 81pass MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_credential accepts 3 parameters: reason, credentialId, confirmationToken. Required: credentialId. 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 revoke_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.
revoke_credential is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_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 revoke_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.
revoke_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.
Across the catalogue