Expose paginated user directory
All clear
No verified vulnerabilities and code craft 273/300.
Security agent
Scripted demo replay
Instead of reading one big prompt, the agent plans, then investigates the code graph one tool call at a time and sees each real result before deciding what to check next.
- 1Inspect the changed function and where its inputs come from
- 2Trace entry points through the change to dangerous calls
- 3Read the code on the path for validation or auth checks
- 4Report only what the evidence supports
- Step 1Looked up
app.routes.users:list_usersStart with the changed symbol.
What it found
{ "id": "app.routes.users:list_users", "kind": "function", "file": "app/routes/users.py", "lines": [ 26, 28 ], "params": [ "limit", "user" ], "entry_point": true, "route": "GET /", "depends_on": [ "get_current_user" ], "untrusted_inputs": [], "dangerous_calls": [], "has_docstring": true } callers: (none) callees: app.auth:get_current_user (app/auth.py:9-15) via line 26 app.services.user_service:UserService (app/services/user_service.py:5-20) via line 28 app.services.user_service:UserService.list_active (app/services/user_service.py:13-20) via line 28