create_mock_endpoint · RequestBin MCP Server MCP

WHAT IT DOES

What create_mock_endpoint does on RequestBin MCP Server

AI agents use create_mock_endpoint to create or update resources in RequestBin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RequestBin MCP Server environment.

WHY IT NEEDS A POLICY

Why create_mock_endpoint needs a policy

This tool creates new mock endpoints and persists configuration rules on RequestBin's servers. While not destructive (the endpoint can be deleted), it does create network-accessible resources and configurable HTTP handlers that could be exploited if an agent creates endpoints with misleading hostnames or response rules.

From the tool's definition The tool "Create a mock API endpoint" that "Returns a live URL ({slug}.rbmock.dev)" and adds starter rules. The description states it creates and configures HTTP response rules, which are new resources being added to an external service.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_mock_endpoint Rate-limited

create_mock_endpoint 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_mock_endpoint": {
      "limits": [
        {
          "counter": "create_mock_endpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RequestBin MCP Server, so you can run agents against it safely.

FAQ

Questions about create_mock_endpoint

What does the create_mock_endpoint tool do? +

Create a mock API endpoint. Returns a live URL ({slug}.rbmock.dev) that responds to HTTP requests with rules you configure. A starter rule (any-method any-path → 200 JSON) is added automatically. Custom slugs require PRO/TEAM; otherwise an auto-slug is generated. It is categorised as a Write tool in the RequestBin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_mock_endpoint? +

Register the RequestBin MCP Server MCP server in PolicyLayer and add a rule for create_mock_endpoint: 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.

What risk level is create_mock_endpoint? +

create_mock_endpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_mock_endpoint? +

Yes. Add a rate_limit block to the create_mock_endpoint 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.

How do I block create_mock_endpoint completely? +

Set action: deny in the PolicyLayer policy for create_mock_endpoint. 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.

What MCP server provides create_mock_endpoint? +

create_mock_endpoint 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.