Publish the current rule set of a mock endpoint to the live mock server. Bumps the configVersion and invalidates edge caches so new requests see the latest rules.
AI agents invoke deploy_mock to trigger actions in RequestBin MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool triggers external operations (publishing to live servers, cache invalidation) whose effects depend on the current rule set configuration. This is an Execute action because it causes side effects on external systems beyond simple data modification.
From the tool's definition Tool description states it will 'Publish the current rule set of a mock endpoint to the live mock server' and 'invalidates edge caches'. This is a deployment/publication action that modifies live infrastructure state.
Attacks that exploit this kind of access
Publish the current rule set of a mock endpoint to the live mock server. Bumps the configVersion and invalidates edge caches so new requests see the latest rules. It is categorised as a Execute tool in the RequestBin MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RequestBin MCP Server MCP server in PolicyLayer and add a rule for deploy_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 RequestBin MCP Server. Nothing to install.
deploy_mock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_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 deploy_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.
deploy_mock is provided by the RequestBin MCP Server MCP server (requestbin/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →