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

wavexis_webauthn_remove_credential

Remove a virtual authenticator.

SERVERPypi:wavexis SOURCEMathiasPaulenko/wavexis-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/wavexis-mcp/wavexis-webauthn-remove-credential.md

What wavexis_webauthn_remove_credential does on Pypi:wavexis

AI agents call wavexis_webauthn_remove_credential to permanently remove resources in Pypi:wavexis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why wavexis_webauthn_remove_credential is rated Critical

Removing a virtual authenticator destroys authentication material. This is a destructive operation with no undo: once removed, the credential is gone and must be re-registered. While the blast radius is scoped to test/virtual environments (not financial systems or user production data), the irreversible nature of deletion and the security sensitivity of authentication credentials elevate this above Execute/Write.

From the tool's definition Tool name contains 'remove' and description states 'Remove a virtual authenticator' — this irreversibly deletes a stored credential that cannot be recovered.

Questions about wavexis_webauthn_remove_credential

What does the wavexis_webauthn_remove_credential tool do? +

Remove a virtual authenticator. It is categorised as a Destructive tool in the Pypi:wavexis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on wavexis_webauthn_remove_credential? +

Register the Pypi:wavexis MCP server in PolicyLayer and add a rule for wavexis_webauthn_remove_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 Pypi:wavexis. Nothing to install.

What risk level is wavexis_webauthn_remove_credential? +

wavexis_webauthn_remove_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 wavexis_webauthn_remove_credential? +

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

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

wavexis_webauthn_remove_credential is provided by the Pypi:wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pypi:wavexis, 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 Pypi:wavexis'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.