burpsuite

Burp Suite Security Testing Skill

Use the native burp-mcp server as a controlled, deterministic interface to Burp Suite. Focus on reproducible security evidence, defensive test isolation, and bounded side effects.

Tool names in this skill are server-local names. Use the exact names returned by the connected server's tools/list; MCP hosts may expose qualified bindings such as mcp__burp_mcp_burp_http or tool.mcp__burp_mcp_burp_http, so do not assume tool.burp_http exists in an eval kernel. The runtime MCP schema is authoritative.

---

Decision Index: When to Load Specific References

Load supporting reference files only when the task enters a specific domain:

Domain / Task	Reference to Load	Purpose
AppSec Testing Methodologies & OAST	references/appsec-testing-guide.md	OWASP WSTG testing techniques for Auth, IDOR, SQLi, XSS, OAST (Collaborator blind SSRF/RCE/XXE/SQLi), Race conditions, and WebSockets.
Complete Tool Schema & Inputs	references/tool-catalog.md	Parameter lists, constraints, and schemas for the current tool runtime.
PortSwigger Desktop Workflows	references/burp-workflows.md	Standard desktop workflows for Proxy, Scope, Repeater, Intruder, and Scanner.
Graph-Based Attack Surface	references/sitegraph.md	SQLite sitegraph partitioning, modes, clustering, shortest path, and impact analysis.
Scanner Custom Checks	references/bcheck-authoring.md	Writing, reviewing, validating, and importing declarative BCheck scripts.
Table Filters & Java Scripts	references/bambda-authoring.md	Writing, reviewing, and importing Java Bambda scripts for Proxy, Logger, and Repeater.

---

Safety Contract & Testing Discipline

1. Verify Authorization: Identify the exact target scheme, host, port, and allowed path boundaries before sending active traffic, fuzzing, crawling, polling Collaborator, or modifying Burp state. Scope is a routing boundary, not legal authorization.
2. Token Efficiency First: Prefer compact metadata history and details (burp_proxy / burp_logger default include_bodies: false, max_body_length: 4096 default). Use server-side projection (headers_only, extract_json: "$.data...", extract_css: "form#login") or explicit capped bodies (include_bodies: true) to preserve client context window. Projections use bounded custom Pest parsers (extract_css with structural/logical pseudos, sibling/child combinators, and :contains; extract_json with negative indexes, slices, recursive descent, and logical filter expressions). Original byte lengths and truncation state are emitted. SiteGraph passive enrichment is separate: its embedded 2026.09.05 typed TOML pack contains 105 ordinary regex rules evaluated by surface-partitioned byte-safe RegexSet matching.
3. Start Read-Only: Prefer Proxy history (burp_proxy action history), Logger traffic (burp_logger action query), Target site map (burp_target action sitemap), target info (burp_target action info), Scanner issues (burp_scanner action list_issues), sitegraph queries (sitegraph action search), and offline decoder operations (decoder) before generating active traffic.
4. Preserve Operator State: Record every temporary scope addition, intercept state change, HTTP handler, proxy rule, session rule, macro, cookie, background job, and managed WebSocket connection. Restore or remove it during cleanup.
5. Interception Discipline: Do not enable proxy interception in unattended flows. Both MCP HTTP (burp_intercept_controller) and WebSocket (burp_websocket_intercept_controller) controllers require a narrow url_filter or in_scope_only: true; both default to RECEIVED-only pauses (preventing duplicate TO_BE_SENT pauses). One logical HTTP exchange may yield request and response items, and one bidirectional WebSocket exchange yields outbound and inbound messages; clients must resolve all intended items, verify pending is zero, and disable the controller. Restore original operator state upon completion.
6. Rate & Concurrency Bounds: Limit parallel requests (at most 32 via burp_http action send_batch), cap scan concurrency via custom resource pools (burp_scan_config action upsert_pool), and pace background job polling.
7. Protect Secrets & Redact Evidence: Never log or disclose private keys, session cookies, auth tokens, or Collaborator secrets in reports.