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

check_credential_status

Check revocation and suspension status of a credential in the Bitstring Status List v1.0

SERVER81pass SOURCE@81pass/mcp-server
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/81pass-mcp-server/check-credential-status.md

What check_credential_status does on 81pass

AI agents call check_credential_status 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.

ParameterTypeRequiredDescription
credentialId string Yes The unique URI or UUID of the credential
statusListIndex number — Optional index in the status list bitstring

Parameters from the server's own tool schema.

Why check_credential_status is rated Low

Even though check_credential_status 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.

Questions about check_credential_status

What does the check_credential_status tool do? +

Check revocation and suspension status of a credential in the Bitstring Status List v1.0. It is categorised as a Read tool in the 81pass MCP Server, which means it retrieves data without modifying state.

What parameters does check_credential_status accept? +

check_credential_status accepts 2 parameters: credentialId, statusListIndex. Required: credentialId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_credential_status? +

Register the 81pass MCP server in PolicyLayer and add a rule for check_credential_status: 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 check_credential_status? +

check_credential_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_credential_status? +

Yes. Add a rate_limit block to the check_credential_status 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 check_credential_status completely? +

Set action: deny in the PolicyLayer policy for check_credential_status. 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 check_credential_status? +

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