// SCAN REPORT

Adaptive LLM Gateway

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 29/06/2026

How to control Adaptive LLM Gateway ↓

TOOL MAP

What Adaptive LLM Gateway exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Adaptive LLM Gateway tools

Execute · High gateway.complete This tool sends prompts to external LLM providers via a gateway, triggering external API calls whose effects depend on the prompt and routing logic.

1 of Adaptive LLM Gateway's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Adaptive LLM Gateway

PolicyLayer is an MCP gateway — it sits between your AI agents and Adaptive LLM Gateway, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "gateway.discover": {
    "limits": [
      {
        "counter": "gateway.discover_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Adaptive LLM Gateway — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ADAPTIVE LLM GATEWAY →

Instant setup, no code required.

FULL CATALOGUE

All 3 Adaptive LLM Gateway tools

EXECUTE 1 tools

Execute gateway.complete Route a prompt through the Adaptive LLM Gateway. Auto-selects model + provider based on task_type and routing

READ 2 tools

Read gateway.discover Return the list of available providers, local LLM servers, and routable models. Read gateway.embed Generate embeddings via the gateway (default backend: local Ollama nomic-embed-text).

FAQ

Questions about Adaptive LLM Gateway

Is the Adaptive LLM Gateway MCP server safe to use without restrictions? +

The Adaptive LLM Gateway server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Adaptive LLM Gateway MCP server expose? +

3 tools across 1 categories: Read. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Adaptive LLM Gateway? +

Register the Adaptive LLM Gateway MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Adaptive LLM Gateway tool call.

Deterministic rules across all 3 Adaptive LLM Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ADAPTIVE LLM GATEWAY →

Instant setup, no code required.

3 Adaptive LLM Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.