// MCP TOOL REFERENCE

MOCKSERVER TOOLS

6 tools from the Mockserver MCP Server, categorised by risk level.

READ TOOLS

mockserver_retrieve_requests Retrieve recorded requests from MockServer. Optionally filter by request matcher. 2/5 mockserver_status Get MockServer connection status and configuration. Returns host, port, and reachability. mockserver_verify Verify that requests matching criteria were received by MockServer. Returns verification result with match count. 2/5

WRITE TOOLS

mockserver_create_expectation Create a mock HTTP expectation on MockServer. Define request matching criteria and the response to return. 3/5

DESTRUCTIVE TOOLS

mockserver_clear Clear expectations and recorded requests from MockServer. Optionally filter by request matcher. 5/5 mockserver_reset Perform a full reset of MockServer, clearing all expectations and recorded requests. 4/5

// FAQ

How many tools does the Mockserver MCP server have? +

The Mockserver MCP server exposes 6 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Mockserver tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Mockserver server.

What risk categories do Mockserver tools fall into? +

Mockserver tools are categorised as Read (3), Write (1), Destructive (2). Each category has a recommended default policy.

Enforce policies on Mockserver

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →