Authz Compare
authz_compareCompare server responses for a URL fetched under two different identities to detect missing authorization checks and report differences.
Instructions
[EXPLOIT — requires human approval] Fetch one URL as two identities and report whether the server told them apart.
The core authorization test. If A can read A's resource and B can read it too, the server is not checking ownership — that is an IDOR. If B is refused, it is.
Restricted to GET and HEAD on purpose. Proving broken access control never requires writing: reading another user's record is the proof, and writing to it modifies data that is not yours, which every program in this space forbids outright.
Reports a CANDIDATE, never a confirmed finding. Two identical responses can also mean the resource is public, or that neither session is actually authenticated. The result says which checks would settle it.
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": {
"target": "<target>",
"session_a": "<session_a>",
"session_b": "<session_b>"
},
"name": "authz_compare"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| method | No | GET | |
| target | Yes | ||
| session_a | Yes | ||
| session_b | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||