generate_from_openapi · API Creator MCP: Risk & Policy

WHAT IT DOES

What generate_from_openapi does on API Creator MCP

AI agents invoke generate_from_openapi to trigger actions in API Creator MCP. 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.

WHY IT NEEDS A POLICY

Why generate_from_openapi needs a policy

This tool does more than write files; it converts a specification into a *working* (i.e., running or deployable) MCP server, which constitutes executing/triggering external operations. It may also generate SDK code artifacts. The blast radius is high because a malicious or malformed OpenAPI spec could result in a rogue MCP server being stood up with unintended endpoints, security misconfigurations, or injected code.

From the tool's definition 'Convert an OpenAPI specification into a working MCP server with optional SDK generation' — this tool generates and instantiates a running MCP server, triggering external operations (server creation, code generation, SDK generation) whose effects depend on…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_from_openapi Rate-limited

generate_from_openapi stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_from_openapi": {
      "limits": [
        {
          "counter": "generate_from_openapi_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about generate_from_openapi

What does the generate_from_openapi tool do? +

Convert an OpenAPI specification into a working MCP server with optional SDK generation. It is categorised as a Execute tool in the API Creator MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_from_openapi? +

Register the API Creator MCP server in PolicyLayer and add a rule for generate_from_openapi: 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 Creator MCP. Nothing to install.

What risk level is generate_from_openapi? +

generate_from_openapi is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit generate_from_openapi? +

Yes. Add a rate_limit block to the generate_from_openapi 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 generate_from_openapi completely? +

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

generate_from_openapi is provided by the API Creator MCP server (tolkyo/api-creator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.