Low Risk

fetch_openapi_spec

Fetches the content of one or more OpenAPI spec URLs.

How to control fetch_openapi_spec ↓

What fetch_openapi_spec does on SushiMCP

AI agents call fetch_openapi_spec to retrieve information from SushiMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_openapi_spec needs a policy

This tool retrieves and queries OpenAPI specification documents from URLs. It performs data retrieval without modifying, deleting, or executing anything. The operation is non-destructive and read-only, making it a Read category tool. Severity is low because accessing publicly available API specifications poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name is 'fetch_openapi_spec' and description states 'Fetches the content of one or more OpenAPI spec URLs.' The verb 'fetches' and the action of retrieving content from URLs are characteristic of read-only operations with no side effects.

Documented attack patterns abuse exactly the kind of access fetch_openapi_spec gives an agent:

How to control fetch_openapi_spec

PolicyLayer is an MCP gateway — it sits between your AI agents and SushiMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_openapi_spec:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_openapi_spec": {}
  }
}

fetch_openapi_spec is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SushiMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_openapi_spec

What does the fetch_openapi_spec tool do? +

Fetches the content of one or more OpenAPI spec URLs. It is categorised as a Read tool in the SushiMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_openapi_spec? +

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

What risk level is fetch_openapi_spec? +

fetch_openapi_spec is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_openapi_spec? +

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

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

fetch_openapi_spec is provided by the Sushi MCP server (maverickg59/sushimcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SushiMCP tool call.

Start from SushiMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 SushiMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.