New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

revoke_credential

Revoke an existing credential in the Bitstring Status List. REQUIRES HUMAN CONFIRMATION.

SERVER81pass SOURCE@81pass/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 31 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

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

Questions about revoke_credential

What does the revoke_credential tool do? +

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.

What parameters does revoke_credential accept? +

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.

How do I enforce a policy on revoke_credential? +

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.

What risk level is revoke_credential? +

revoke_credential is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit revoke_credential? +

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.

How do I block revoke_credential completely? +

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.

What MCP server provides revoke_credential? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 81pass's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.