wavexis_webauthn_remove_credential
Remove a virtual authenticator.
This record as markdown: /tools/wavexis-mcp/wavexis-webauthn-remove-credential.md
What wavexis_webauthn_remove_credential does on Wavexis
AI agents call wavexis_webauthn_remove_credential to permanently remove resources in 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.
Attacks that exploit this kind of access
The rule that runs wavexis_webauthn_remove_credential safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_webauthn_remove_credential, this is the rule to start with:
wavexis_webauthn_remove_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 Wavexis, apply this rule, and every wavexis_webauthn_remove_credential call is checked against it from then on.
Questions about wavexis_webauthn_remove_credential
Remove a virtual authenticator. It is categorised as a Destructive tool in the Wavexis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 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 Wavexis. Nothing to install.
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.
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.
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.
wavexis_webauthn_remove_credential is provided by the 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 Wavexis, and thousands of servers like it.
Across the catalogue