api_auth_bypass_test
Test for authentication bypass vulnerabilities.
This record as markdown: /tools/zebbern-zebbern-kali-mcp/api-auth-bypass-test.md
What api_auth_bypass_test does on Zebbern Kali MCP
AI agents invoke api_auth_bypass_test to trigger actions in Zebbern Kali MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why api_auth_bypass_test is rated High
This tool actively tests for authentication bypass vulnerabilities, meaning it executes attack techniques against authentication systems. It is not a passive read — it probes/attempts to bypass auth mechanisms. In the context of a Kali Linux pentest server, 'test' means actively running exploits or bypass attempts.
From the tool's definition 'Test for authentication bypass vulnerabilities' on a Kali Linux penetration testing toolkit with direct container access
Attacks that exploit this kind of access
The rule that runs api_auth_bypass_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zebbern Kali MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_auth_bypass_test, this is the rule to start with:
api_auth_bypass_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zebbern Kali MCP, apply this rule, and every api_auth_bypass_test call is checked against it from then on.
Questions about api_auth_bypass_test
Test for authentication bypass vulnerabilities. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for api_auth_bypass_test: 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 Zebbern Kali MCP. Nothing to install.
api_auth_bypass_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the api_auth_bypass_test 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 api_auth_bypass_test. 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.
api_auth_bypass_test is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zebbern Kali, and thousands of servers like it.
Across the catalogue