get_optimization_history
AI agents call get_optimization_history to retrieve information from Sablier MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to fetch or retrieve previously computed optimization results. This is a Read operation — it retrieves data without modifying, deleting, or executing external side effects. Severity is low because reading historical data poses minimal risk even if invoked incorrectly; confidence is moderate (0.85) due to the empty description, which prevents full certainty of the tool's exact behavior.
From the tool's definition Tool name 'get_optimization_history' indicates retrieval of historical optimization data with no mutation. The 'get_' prefix is a standard Read pattern (query, list, get, fetch).
Attacks that exploit this kind of access
get_optimization_history. It is categorised as a Read tool in the Sablier MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for get_optimization_history: 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 Sablier MCP Server. Nothing to install.
get_optimization_history 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_optimization_history 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_optimization_history. 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_optimization_history is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-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 →