A Practical Security Pass for Your LangChain Agent Project

LangChain is how many teams assemble their first production agent: a model, a set of tools, memory, and retrieval, chained together. Every tool you wire in and every configuration file you add expands what the agent — and the AI coding assistants you use to build it — can reach. This guide walks through a concrete security pass over that surface using DeepSweep's free tooling.

First, an honest scope note. DeepSweep is not a runtime wrapper for your chains — there is no package to import into your LangChain code, and nothing below changes how your agent executes. What DeepSweep validates is the agent environment around your project: the configuration files that give coding assistants and MCP servers their instructions and their reach, and the AI-generated code they produce. Everything below runs locally against the files in your repository.

Where LangChain Projects Accumulate Risk

A LangChain repository rarely contains only LangChain code. It usually also carries the working files of the assistants that helped build it: rules files like .cursorrules or copilot instructions that steer a coding agent on every request, MCP configurations such as mcp.json that hand tools filesystem or shell reach, and generated tool code that nobody read as closely as hand-written code. Each of these is an attack surface. A poisoned rules file quietly redirects your coding agent; an unverified MCP server is a supply-chain risk with real system access. These are the same mechanisms behind the tool-poisoning and rules-file attacks documented across the industry in 2025.

Step 1: Validate the Project

Install the CLI with pip install deepsweep-ai — note the name; it installs the deepsweep command. Then, from your project root, run: deepsweep validate .

The CLI loads its detection rules (16 focused rules in the current release, covering instruction override in rules files, MCP server poisoning, exfiltration directives, and related agent-configuration risks) and reviews the AI assistant configuration files in your project. Findings come back in plain English with the exact file and line, why it matters, and a fix you can paste straight to your coding assistant. The run ends with a letter grade for the project.

To include MCP configuration checking explicitly, run: deepsweep validate . --include-mcp

On a typical LangChain project this is where the surprises surface. In a test project we wired a filesystem MCP server the way many tutorials do — unpinned, from an unverified source, rooted at / — and the validation flagged it at the exact line: an unverified MCP server and an unpinned version, each with a one-line fix. That is the kind of finding that never appears in a code review, because the reviewer is looking at your chains, not your agent wiring.

Step 2: Catch Issues While You Build

The DeepSweep editor extension runs the same class of checks as you edit, inside VS Code, Cursor, and Windsurf. It is published on the Open VSX registry: https://open-vsx.org/extension/deepsweep-ai/deepsweep

The extension ships 77 detection patterns — 37 AI-specific plus 40 traditional code-security patterns — including 7 prompt-injection rules and 7 MCP rules. It validates assistant configuration files and generated code as you work, so a poisoned rules file or a risky MCP entry is flagged before it is ever committed.

Step 3: Gate Your CI

The CLI exits non-zero when findings meet a severity you choose, which makes the pipeline gate a one-liner: deepsweep validate . --fail-on critical

If your code host ingests SARIF, you can emit a report for it: deepsweep validate . --format sarif --output deepsweep.sarif

Step 4: Review the Wider Agent Environment

Validation covers the files in one repository. The free Agent Environment Review at https://deepsweep.ai/review takes the broader view: what your agents can actually do, what they have been authorized to do, and where the gaps between those two sets are.

None of this requires changing your LangChain code. The risk in agent projects concentrates in the environment around the chains — the instructions, the tool wiring, the generated code — and that surface is checkable today, locally, for free. Full documentation is at https://deepsweep.ai/docs