Skip to content

docs(cloud-security): IDE & MCP page (P3.3) — HOLD OPEN - #361

Draft
maximelb wants to merge 1 commit into
masterfrom
docs/cloud-security-mcp-ide
Draft

docs(cloud-security): IDE & MCP page (P3.3) — HOLD OPEN#361
maximelb wants to merge 1 commit into
masterfrom
docs/cloud-security-mcp-ide

Conversation

@maximelb

Copy link
Copy Markdown
Contributor

HOLD OPEN — do not merge. Docs for roadmap 15 P3.3, held for the docs round alongside #355 and #360.

Adds docs/cloud-security/mcp.md and a nav entry after Command Line Interface: setup for Claude Code and Cursor, the profiles, the permissions, and the four AppSec code-lane tools.

Depends on lc-mcp-server#58, which is ready for review and not yet merged. Nothing on this page is true until that ships — merge order is lc-mcp-server#58, then this.

The page leads with the two things that surprise people rather than burying them:

  • cloudsec_code_findings will not list without a repository. The findings backend has no "any repository" selector, so an unscoped call would quietly return the reader's whole worklist, cloud findings included, under a tool named for the code lane. facets: true is the unscoped mode.
  • cloudsec_code_scan_local runs on the reader's own machine, needs Docker, takes minutes, and cannot scan for secrets — a credential's identity is a digest keyed by a value only the hosted lane holds.

It also documents the repo key trap found while testing: the filter is matched exactly against a key whose owner segment carries the connection's configured casing, while a finding's code.repo_name is the platform's display casing.

Deliberately not linked to code-scanning.md: that page is itself unmerged (#355), so this page links only to files already on master.

🤖 Generated with Claude Code

Setup for Claude Code and Cursor, the profiles, and the four AppSec code-lane
tools — including the two things that surprise people: cloudsec_code_findings
will not list without a repository (the backend has no 'any repository'
selector, so an unscoped list would quietly return the cloud worklist too), and
cloudsec_code_scan_local runs a container on the reader's OWN machine, needs
Docker, and cannot scan for secrets.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@maximelb

Copy link
Copy Markdown
Contributor Author

Superseded by #362, which consolidates this branch with the other code-lane docs branches into one page set off master and reconciles every claim against the shipped code (nine differences are listed in that PR's body). Leaving this open rather than closing it — Maxime closes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants