get_started_guide
AI agents call get_started_guide to retrieve information from Ollama_MCP_Guidance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name contains 'get_' prefix, which typically indicates a read/retrieval operation with no side effects. The absence of any mutation, execution, or deletion language supports a Read classification. However, confidence is reduced due to empty description and unknown parameter behavior. If the tool actually executes scripts or performs operations beyond simple retrieval, it could be Execute instead.
From the tool's definition Tool name 'get_started_guide' suggests retrieval of documentation or guidance content. Description is empty, making classification more difficult.
Attacks that exploit this kind of access
get_started_guide. It is categorised as a Read tool in the Ollama_MCP_Guidance MCP Server, which means it retrieves data without modifying state.
Register the Ollama_MCP_Guidance MCP server in PolicyLayer and add a rule for get_started_guide: 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.
get_started_guide is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_started_guide 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 get_started_guide. 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.
get_started_guide 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 →