simple_generate
AI agents invoke simple_generate to trigger actions in Ollama_MCP_Guidance. 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.
Given the server context (Ollama API interactions) and the naming pattern of sibling tools (simple_chat, post_generate_embeddings, etc.), 'simple_generate' most likely triggers LLM text generation via Ollama, which is an Execute-class operation (runs an external model inference call). The empty description lowers confidence, but the pattern is consistent with Execute.
From the tool's definition Tool name 'simple_generate' on a server that interacts with Ollama API for LLM-based API calls; description is empty.
Attacks that exploit this kind of access
simple_generate. It is categorised as a Execute tool in the Ollama_MCP_Guidance MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ollama_MCP_Guidance MCP server in PolicyLayer and add a rule for simple_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 Ollama_MCP_Guidance. Nothing to install.
simple_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 simple_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 simple_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.
simple_generate is provided by the Ollama_MCP_Guidance MCP server (shadovvsinger/ollama_mcp_guidance). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →