mcpField
S
Shieldmcp

Shieldmcp

Local
github.com/shieldmcpSecurity3Updated 82w ago

About Shieldmcp

Shieldmcp is security middleware for MCP servers during development, helping developers control tool calls and monitor activity. It adds access controls, output sanitization, audit logging, and rate limiting without modifying the official SDK.

Key features

  1. 01Whitelist tool access
  2. 02Sanitize tool outputs
  3. 03Record structured audit logs
  4. 04Apply token-bucket rate limits
  5. 05Standardize error handling

Use cases

  1. 01Restrict which tools can be called
  2. 02Filter sensitive output
  3. 03Track tool calls and failures
  4. 04Limit tool-call frequency

MCP support

Shieldmcp adds security and monitoring to MCP tool calls without replacing or modifying the official SDK, and is compatible with MCP Inspector.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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 shieldmcp

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.