Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Audit] Medium — MCP cross-scan depth and sweep are unbounded

Open
#726 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@pchukwuemeka424 is already working on this.

Since Oct 26, 2026.

  • #750 by @pchukwuemeka424 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
security

Research direction

Start with the named schema and handler locations, then trace how depth and sweep reach user_scanner/core/cross_scan.py:105-180. The issue calls for conservative limits and a shared request fan-out budget across rounds and target types. Add tests showing excessive values fail before scanning and a fake pivot graph cannot exceed the validator-call budget.

Written by the indexing model from the issue text.

Description

  • Location: user_scanner/mcp/schemas.py:38-51, user_scanner/mcp/handlers.py:85-89,142-152,
    and user_scanner/core/cross_scan.py:105-180.
  • Defect / trigger: schema and handler impose no maximum. depth drives serial rounds and
    sweep authorizes repeated all-module passes across thousands of vectors.
  • Impact / root cause / evidence: an agent mistake or hostile tool request can cause enormous
    outbound traffic, cost, runtime, and collection of unrelated people's data.
  • Smallest robust correction: enforce conservative maximums and an overall request/fan-out
    budget shared across rounds and target types.
  • Proving test: excessive depth/sweep fails before scanning; a fake pivot graph proves the total
    validator-call budget cannot be exceeded.
  • Confidence: high.
  • LLM-agent warning: Keep investigating. Model total fan-out, not each knob independently;
    permutations, domains, modules, redirects, media, and pivots multiply one another.
Dominant language
Python
Stars
5.2k
Forks
530
Avg merge
23h 52m
Merged PRs (30d)
43

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kaifcodec/user-scanner

All issues in kaifcodec/user-scanner

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.