// SCAN REPORT

Local Llm Delegation

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

2 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

2 can modify or destroy data

1 read-only

3 tools total

Community server · catalogue entry verified 02/07/2026

How to control Local Llm Delegation ↓

TOOL MAP

What Local Llm Delegation exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Local Llm Delegation tools

Execute · Medium query_local_llm This tool executes a query against a local LLM, which runs an external computational process. Execute · Medium query_local_llm_with_context This tool executes queries against a local LLM, passing context and arguments that influence its behavior.

2 of Local Llm Delegation'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 Local Llm Delegation

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

Cap read operations

{
  "get_local_llm_usage_stats": {
    "limits": [
      {
        "counter": "get_local_llm_usage_stats_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 Local Llm Delegation — 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 LOCAL LLM DELEGATION →

Instant setup, no code required.

FULL CATALOGUE

All 3 Local Llm Delegation tools

EXECUTE 2 tools

Execute query_local_llm Query the local LLM for simple, well-defined subtasks that have already been broken down. Execute query_local_llm_with_context Query the local LLM for simple subtasks that require additional context.

READ 1 tools

Read get_local_llm_usage_stats Retrieve and summarize usage statistics for the local LLM MCP server.

FAQ

Questions about Local Llm Delegation

Is the Local Llm Delegation MCP server safe to use without restrictions? +

The Local Llm Delegation server is primarily read-only with 1 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 Local Llm Delegation MCP server expose? +

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

How do I enforce a policy on Local Llm Delegation? +

Register the Local Llm Delegation 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 Local Llm Delegation tool call.

Deterministic rules across all 3 Local Llm Delegation tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LOCAL LLM DELEGATION →

Instant setup, no code required.

3 Local Llm Delegation tools catalogued and risk-classified — across an index of 43,000+ MCP servers.