Forbidden Bypass
forbidden_bypassTest a 403-forbidden URL against twelve access-bypass techniques to find a working bypass, returning the first success with a curl PoC or a clean report.
Instructions
[AGGRESSIVE — requires human approval] Test a URL that returned 403 against twelve access-bypass techniques.
url must be a URL that actually returned 403 (run forbidden_candidates
or check the probe result first — unKover refuses anything else).
prefix optionally adds an API version prefix (/v2) that the server
may not protect. Returns the first working technique with a curl PoC, or a
clean report when nothing bypasses.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"url": "<url>"
},
"name": "forbidden_bypass"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| prefix | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||