post_show_model
AI agents call post_show_model 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.
Based on the tool name and context of sibling tools (list_models, get_ollama_list, get_running_models), this tool likely shows/retrieves details about a specific model. The 'post_' prefix indicates it uses an HTTP POST method but the action is likely a read/query operation. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'post_show_model' suggests it retrieves/displays model information via a POST request to Ollama API; description is empty and uninformative.
Attacks that exploit this kind of access
post_show_model. 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 post_show_model: 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.
post_show_model 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 post_show_model 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 post_show_model. 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.
post_show_model 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 →