mcp-bastion-langchain
Security middleware for LangChain powered by MCP-Bastion.
Protects your LangChain agents from prompt injection, PII leakage, and resource exhaustion.
Install
pip install mcp-bastion-langchain
Usage
Callback (automatic protection)
from langchain_openai import ChatOpenAI
from mcp_bastion_langchain import BastionSecurityCallback
llm = ChatOpenAI(callbacks=[BastionSecurityCallback()])
llm.invoke("Hello, what is MCP?")
Tool decorator
from mcp_bastion_langchain import secure_tool
@secure_tool
def my_tool(query: str) -> str:
return f"Result for {query}"
Features
- Content filtering on all LLM prompts and tool inputs
- Rate limiting per caller
- Prompt injection detection
- PII redaction
License
Same terms as the MCP-Bastion project: see LICENSE. Non-commercial use is free with required citation/attribution; copyright terms apply. Commercial use as defined in the License may need a separate agreement (COMMERCIAL_LICENSE.md).
1 maintainer
Metadata
1 maintainer
Release files for mcp-bastion-langchain 5.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_bastion_langchain-5.1.0.tar.gz | 3.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_bastion_langchain-5.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.9 kB
Release files / mcp_bastion_langchain-5.1.0.tar.gz
| Download URL | mcp_bastion_langchain-5.1.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cadd80fb113b3782de85e56fd7782bb27e6e03544c661285fed189023269a591
|
|
BLAKE2b-256 checksum How to use checksums |
f45fdf36b77eeb7d4e768db23217f906c09775c4e5405fc6b48c4f8347cfb25f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency logRelease files / mcp_bastion_langchain-5.1.0-py3-none-any.whl
| Download URL | mcp_bastion_langchain-5.1.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d08ca76a6de387ef92cd29c4f1db76cb72c19ac6cb3334ae704428a5acfb5d4
|
|
BLAKE2b-256 checksum How to use checksums |
9b7c2202c9d52b2328c88a20768fb4b7261fc06444a2865cae852d08a24dfa44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency logSecurity for mcp-bastion-langchain 5.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_bastion_langchain-5.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
