Skip to main content

Shield MCP

Python Version License MCP Compatible

A security middleware for Model Context Protocol (MCP) servers that enhances security and monitoring capabilities without modifying the official SDK. This package provides tools for securing and monitoring MCP tool calls, following the best practices outlined in the MCP documentation. Abstract yourself while interact at MCP development.

Table of Contents

Features

  • Tool Access Control: Whitelist-based access control for MCP tools
  • Result Sanitization: Configurable sanitization of tool outputs
  • Structured Logging: Comprehensive audit logging using structlog
  • Rate Limiting: Token bucket algorithm for rate limiting
  • Error Handling: Standardized error handling and formatting
  • MCP Inspector Compatible: Works seamlessly with the MCP Inspector tool

Requirements

System Requirements

  • Python 3.8 or higher
  • pip (Python package installer)
  • virtualenv (recommended for development)

Quick Start

from shieldmcp import secure_tool
from shieldmcp.sanitizers import ToolSanitizer
from shieldmcp.rate_limit import RateLimitConfig

# Define allowed tools
ALLOWED_TOOLS = {"search", "read_file", "write_file"}

# Create a text sanitizer
text_sanitizer = ToolSanitizer.createTextSanitizer(
    max_length=1000,
    sensitive_patterns=[
        r"\b\d{16}\b",  # Credit card numbers
        r"\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b"  # Email addresses
    ]
)

# Configure rate limiting
rate_limit = RateLimitConfig(
    requests_per_minute=60,  # 1 request per second
    burst_size=10  # Allow bursts of up to 10 requests
)

# Apply the decorator to your MCP tools
@secure_tool(
    allowed_tools=ALLOWED_TOOLS,
    sanitize_fn=text_sanitizer,
    user_id="user123",
    session_id="session456",
    rate_limit=rate_limit
)
def search(query: str):
    # Your tool implementation
    return results

Components

Decorators (decorators.py)

The main @secure_tool decorator that orchestrates all security features:

@secure_tool(
    allowed_tools={"tool1", "tool2"},  # Set of allowed tool names
    sanitize_fn=your_sanitizer,        # Optional result sanitization function
    user_id="user123",                 # Optional user identifier
    session_id="session456",           # Optional session identifier
    rate_limit=RateLimitConfig(        # Optional rate limit configuration
        requests_per_minute=60,
        burst_size=10
    )
)
def your_tool():
    pass

Audit Logging (audit.py)

Structured logging using structlog:

from shieldmcp import ToolAudit

audit = ToolAudit()
audit.logToolCallStart(
    tool_name="search",
    args={"query": "test"},
    user_id="user123"
)

Access Control (access.py)

Tool access validation:

from shieldmcp import ToolAccess

access = ToolAccess(allowed_tools={"tool1", "tool2"})
access.validateToolAccess("tool1")  # Raises ValueError if not allowed

Sanitizers (sanitizers.py)

Result sanitization utilities:

from shieldmcp import ToolSanitizer

# Create a custom sanitizer
sanitizer = ToolSanitizer.createTextSanitizer(
    max_length=1000,
    sensitive_patterns=[r"\b\d{16}\b"]
)

# Use it directly
clean_text = sanitizer("Your text with sensitive data")

Rate Limiting (rate_limit.py)

Token bucket rate limiting:

from shieldmcp import RateLimitConfig

# Configure rate limits
config = RateLimitConfig(
    requests_per_minute=60,
    burst_size=10
)

Best Practices

Tool Access Control

  • Always define a whitelist of allowed tools
  • Use the most restrictive set of tools possible
  • Regularly review and update the whitelist

Result Sanitization

  • Sanitize all text output
  • Define patterns for sensitive data
  • Set reasonable length limits

Logging

  • Include user and session IDs when available
  • Log both successful and failed operations
  • Use structured logging for better analysis

Rate Limiting

  • Set appropriate limits based on tool complexity
  • Consider burst sizes for better user experience
  • Monitor rate limit hits in logs

Development

Setup Development Environment

# Clone the repository
git clone https://github.com/shieldmcp/shieldmcp.git
cd modelShield

# Create virtual environment
python -m venv venv
source venv/bin/activate  # or `venv\Scripts\activate` on Windows

# Install development dependencies
pip install -r requirements.txt

Running Tests

pytest tests/

Roadmap

Planned Features

  • Support for Clerk MCP and Github MCP
  • Extended documentation
  • TypeScript support

Acknowledgments


Feel free to make any inquiries.

Metadata

Release files for shieldmcp 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for shieldmcp 0.1.1
File Size Uploaded Provenance
shieldmcp-0.1.1.tar.gz 4.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for shieldmcp 0.1.1
File Interpreter ABI Platform
shieldmcp-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 8.4 kB

Release files / shieldmcp-0.1.1.tar.gz

Download URL shieldmcp-0.1.1.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
9ac9c147760eb757ca440b0ca9af86a89adff958c9913db4eb8a211bdc03dfb4
BLAKE2b-256 checksum
How to use checksums
2a82522f41b37c4d59d8f3cb44163d3a0dc36d380d2e055576bb369d08e92d11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.13.2

Release files / shieldmcp-0.1.1-py3-none-any.whl

Download URL shieldmcp-0.1.1-py3-none-any.whl
Size 3.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fdadbf3c1275703d49953789d06262cb4aa803e3d867cea8cdbfc7ec030e289c
BLAKE2b-256 checksum
How to use checksums
ea1ae8882cf933fef8096c4719a660f625ff4f624212994df063a6424f918009
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.13.2

Security for shieldmcp 0.1.1

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page