Attach a mock to a test case's mock-mapping doc. Use this when the dev has authored a mock (via create_mock or capture) and wants the runtime to actually consume it when replaying a specific test case. Idempotent — re-linking an already-linked mock is a no-op (no duplicate entry). branch_id is RE...
Part of the Keploy server.
Free to start. No card required.
AI agents call link_mock to retrieve information from Keploy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though link_mock only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"link_mock": {}
}
}See the full Keploy policy for all 103 tools.
These attack patterns abuse exactly the kind of access link_mock gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Attach a mock to a test case's mock-mapping doc. Use this when the dev has authored a mock (via create_mock or capture) and wants the runtime to actually consume it when replaying a specific test case. Idempotent — re-linking an already-linked mock is a no-op (no duplicate entry). branch_id is REQUIRED — direct writes to main via MCP are blocked. Mirror tool: unlink_mock.. It is categorised as a Read tool in the Keploy MCP Server, which means it retrieves data without modifying state.
Register the Keploy MCP server in PolicyLayer and add a rule for link_mock: 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 Keploy. Nothing to install.
link_mock is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the link_mock 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 link_mock. 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.
link_mock is provided by the Keploy MCP server (https://api.keploy.io/client/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 103 Keploy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.