특정 엔드포인트의 응답을 수정하거나 새 엔드포인트를 추가합니다.
Risk signalsAccepts file system path (path)
Part of the Api Mock Server server.
Free to start. No card required.
AI agents use update_mock_response to create or modify resources in Api Mock Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_mock_response repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Api Mock Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_mock_response": {
"limits": [
{
"counter": "update_mock_response_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Api Mock Server policy for all 6 tools.
These attack patterns abuse exactly the kind of access update_mock_response gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
특정 엔드포인트의 응답을 수정하거나 새 엔드포인트를 추가합니다.. It is categorised as a Write tool in the Api Mock Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Api Mock Server MCP server in PolicyLayer and add a rule for update_mock_response: 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 Api Mock Server. Nothing to install.
update_mock_response 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 update_mock_response 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 update_mock_response. 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.
update_mock_response is provided by the Api Mock Server MCP server (https://api.lazy-mac.com/api-mock-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Api Mock Server 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.