local_llm_generate
Generate text using a local Ollama model. Runs entirely on your machine — no data sent to any cloud.
This record as markdown: /tools/heznpc-airmcp/local-llm-generate.md
What local_llm_generate does on AirMCP
AI agents invoke local_llm_generate to trigger actions in AirMCP. 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 local_llm_generate is rated High
This tool executes a local LLM (Ollama) on the machine to generate text. It triggers an external computation process whose effects depend on the arguments provided (prompt, model, parameters). While it doesn't directly modify data or move money, it runs code/model inference locally, classifying it as Execute.
From the tool's definition Generate text using a local Ollama model. Runs entirely on your machine
Attacks that exploit this kind of access
The rule that runs local_llm_generate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For local_llm_generate, this is the rule to start with:
local_llm_generate 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every local_llm_generate call is checked against it from then on.
Questions about local_llm_generate
Generate text using a local Ollama model. Runs entirely on your machine — no data sent to any cloud. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for local_llm_generate: 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 AirMCP. Nothing to install.
local_llm_generate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the local_llm_generate 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.
Set action: deny in the PolicyLayer policy for local_llm_generate. 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.
local_llm_generate is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue