Create a conversation; optionally seeds initial user message
AI agents invoke ollama_start_conversation to trigger actions in Promethean OS MCP. 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.
Although this tool does not destructively delete data or move money, it executes operations external to data read/write—it triggers ollama inference processes. The tool's effect (conversation initiation and message processing) depends on provided arguments and causes external state changes in the ollama runtime.
From the tool's definition The tool name 'ollama_start_conversation' and description 'Create a conversation; optionally seeds initial user message' indicate it initiates a new conversation session.
Attacks that exploit this kind of access
Create a conversation; optionally seeds initial user message. It is categorised as a Execute tool in the Promethean OS MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Promethean OS MCP server in PolicyLayer and add a rule for ollama_start_conversation: 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 Promethean OS MCP. Nothing to install.
ollama_start_conversation 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 ollama_start_conversation 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 ollama_start_conversation. 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.
ollama_start_conversation is provided by the Promethean OS MCP server (octave-commons/mcp). 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 →