Provide mock response data for a claimed batch. You MUST first call claim_next_batch to get the batchId and claimToken. The mocks array must contain exactly one mock for each request in the batch.
AI agents use provide_batch_mock_data to create or update resources in Mock — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mock environment.
This tool writes/submits mock data to the server for a previously claimed batch. It creates new data records (mock responses) associated with a batch. It is reversible in principle (data could be overwritten or replaced), so Write is appropriate rather than Destructive. Misuse could result in incorrect mock data being used in tests, but the blast radius is limited to testing environments.
From the tool's definition 'Provide mock response data for a claimed batch' - creates/submits mock data for a batch of requests
Documented attack patterns abuse exactly the kind of access provide_batch_mock_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mock, and nothing reaches the server without passing your rules. This is the rule we recommend for provide_batch_mock_data:
{
"version": "1",
"default": "deny",
"tools": {
"provide_batch_mock_data": {
"limits": [
{
"counter": "provide_batch_mock_data_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}provide_batch_mock_data stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Provide mock response data for a claimed batch. You MUST first call claim_next_batch to get the batchId and claimToken. The mocks array must contain exactly one mock for each request in the batch. It is categorised as a Write tool in the Mock MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mock MCP server in PolicyLayer and add a rule for provide_batch_mock_data: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mock. Nothing to install.
provide_batch_mock_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the provide_batch_mock_data rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for provide_batch_mock_data. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
provide_batch_mock_data is provided by the Mock MCP server (mcpland/mock-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mock, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Mock tools catalogued and risk-classified — across an index of 43,000+ MCP servers.