Skip to main content

MCP Tool Override Server

A Model Context Protocol server implementation that demonstrates how tools can be dynamically overridden across multiple servers.

Overview

This project implements a Model Context Protocol (MCP) server that registers tools using the same names as existing server tools to demonstrate how tools can be dynamically overridden when a new server is added to the configuration.

How It Works

I simply added an MCP Tool Override tester MCP to mimic the tools of other servers. Surprisingly, they are easily overriden by the new tools (which are fake).

┌───────────┐     ┌────────────────────────────────────┐  
│ MCP Client│     │ MCP Tool Servers                   │  
│  (Claude  │────▶│ - File System MCP                  │  
│  Desktop) │     │    - Tool: read_file, ...          │  
└───────────┘     │ - Gmail MCP                        │  
                  │   - Tool: send_email, ...          │  
                  │ - Slack MCP                        │  
                  │   - Tool: slack_list_channels, ... │  
                  │ - MCP Tool Override Tester         │  
                  │   - Tool: read_file, send_email    │  
                  │        and slack_list_channels     │  
                  └────────────────────────────────────┘  

The Claude Desktop still confuses even after all tools of the Override tester MCP are turned off.

Usage

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-slack"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "YOUR SLACK BOT TOKEN",
        "SLACK_TEAM_ID": "YOUR SLACK TEAM ID",
        "SLACK_CHANNEL_IDS": "CHANNEL1_ID, CHANNEL2_ID, ..."
      }
    },
    "gmail": {
      "command": "npx",
      "args": [
        "@gongrzhe/server-gmail-autoauth-mcp"
      ]
    },
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/your/directory/path/to/allow"
      ]
    },
    "override_tester": {
      "command": "/path/to/your/uvx",
      "args": [
        "--from",
        "mcp-tool-override-tester",
        "override_mcp_tools"
      ]
    }
  }
}

License

This project is licensed under the MIT License.

Metadata

Release files for mcp-tool-override-tester 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 mcp-tool-override-tester 0.1.1
File Size Uploaded Provenance
mcp_tool_override_tester-0.1.1.tar.gz 2.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-tool-override-tester 0.1.1
File Interpreter ABI Platform
mcp_tool_override_tester-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 6.3 kB

Release files / mcp_tool_override_tester-0.1.1.tar.gz

Download URL mcp_tool_override_tester-0.1.1.tar.gz
Size 2.9 kB
Tags Source
SHA-256 checksum
How to use checksums
da6312bad0409ff0993c97e842a08b16aecd662d37b19e94ea823100aa58dca8
BLAKE2b-256 checksum
How to use checksums
27e171832f3ce1ee07685a3286fae80dfbc3074f2550da8fae30c3634a02320c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.11.8

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

Download URL mcp_tool_override_tester-0.1.1-py3-none-any.whl
Size 3.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cf23fff7e2d8151f52ca173d9974440a6007ad0bcc5c292a6772c2569919dd5e
BLAKE2b-256 checksum
How to use checksums
440a7d9fd94e6ca1b2edb3bb811e8e7d534632ff771360dd83ad2532541e1193
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.11.8

Security for mcp-tool-override-tester 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