AI agents call clear_auth to permanently remove resources in CyberMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Given the server's security testing focus and the auth-related sibling tools, 'clear_auth' most likely clears authentication tokens, credentials, or session data. This is irreversible (cannot be undone without re-authentication) and affects system security state, making it Destructive rather than merely Write. In a security testing context, this could permanently invalidate sessions.
From the tool's definition Tool name 'clear_auth' with empty description; context from sibling tools (api_login, auth_bypass_check, jwt_vulnerability_check, oauth2_auth) suggests authentication state management.
Documented attack patterns abuse exactly the kind of access clear_auth gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CyberMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_auth:
{
"version": "1",
"default": "deny",
"hide": [
"clear_auth"
]
}clear_auth disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
clear_auth. It is categorised as a Destructive tool in the CyberMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cyber MCP server in PolicyLayer and add a rule for clear_auth: 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 CyberMCP. Nothing to install.
clear_auth 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 clear_auth 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 clear_auth. 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.
clear_auth is provided by the Cyber MCP server (ricauts/cybermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CyberMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 CyberMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.