// SCAN REPORT

Model Drive Protocol MCP Server

4 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

2 can modify or destroy data

2 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control Model Drive Protocol MCP Server ↓

TOOL MAP

What Model Drive Protocol MCP Server exposes to your agents

Read (2) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Model Drive Protocol MCP Server tools

Execute · High callPath The parent server description indicates this bridge exposes 'runtime-local capabilities from browsers, apps, devices, and local processes.' Invoking an arbitrary 'path' on such clients is equivalent to Execute: the tool Execute · High callPaths The tool invokes paths on live clients including browsers, applications, and devices.

2 of Model Drive Protocol MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Model Drive Protocol MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Model Drive Protocol MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "listClients": {
    "limits": [
      {
        "counter": "listclients_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Model Drive Protocol MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MODEL DRIVE PROTOCOL →

Free to start. No card required.

FULL CATALOGUE

All 4 Model Drive Protocol MCP Server tools

EXECUTE 2 tools

Execute callPath Invoke one exact path on one exact MDP client. Execute callPaths Invoke one path on one or more MDP clients.

READ 2 tools

Read listClients List currently connected MDP clients and their path catalogs. Read listPaths List path descriptors registered by connected MDP clients.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Model Drive Protocol MCP Server

Is the Model Drive Protocol MCP Server MCP server safe to use without restrictions? +

The Model Drive Protocol MCP Server server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Model Drive Protocol MCP Server MCP server expose? +

4 tools across 2 categories: Execute, Read. 2 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Model Drive Protocol MCP Server? +

Register the Model Drive Protocol MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Model Drive Protocol MCP Server tool call.

Deterministic rules across all 4 Model Drive Protocol MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MODEL DRIVE PROTOCOL →

Free to start. No card required.

4 Model Drive Protocol MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.