// MCP TOOL REFERENCE

MOCK TOOLS

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

// ALL 6 MOCK TOOLS

READ 3 tools

Read get_batch Get details of a specific batch by ID (read-only, does not claim). Read get_status Get the current status of the mock-mcp daemon, including active test runs and pending batches. Read list_runs List all active test runs connected to the daemon.

WRITE 3 tools

Write claim_next_batch Claim the next pending mock batch for processing. This acquires a lease on the batch. You MUST call th... Write provide_batch_mock_data Provide mock response data for a claimed batch. You MUST first call claim_next_batch to get the batchI... Write release_batch Release a claimed batch without providing mock data. Use this if you cannot generate appropriate mocks.

// FAQ

How many tools does the Mock MCP server have? +

The Mock MCP server exposes 6 tools across 2 categories: Read, Write.

How do I enforce policies on Mock tools? +

Route the Mock server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Mock tools fall into? +

Mock tools are categorised as Read (3), Write (3). Each category has a recommended default policy.

Enforce policy on every Mock tool call.

Start from Mock, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.