AI agents call plot_optimization_history to retrieve information from Optuna MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve and visualize historical optimization results from an Optuna study. Visualization and data retrieval operations fall under the Read category. While the description is missing, the name and context strongly suggest passive analysis of existing optimization records, with no side effects on the study state, no execution of code, and no data modification or deletion.
From the tool's definition Tool name 'plot_optimization_history' suggests visualization/retrieval of historical optimization data. No destructive, write, execute, or financial operations are implied.
Documented attack patterns abuse exactly the kind of access plot_optimization_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Optuna MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for plot_optimization_history:
{
"version": "1",
"default": "deny",
"tools": {
"plot_optimization_history": {}
}
}plot_optimization_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
plot_optimization_history. It is categorised as a Read tool in the Optuna MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Optuna MCP Server MCP server in PolicyLayer and add a rule for plot_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 Optuna MCP Server. Nothing to install.
plot_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 plot_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 plot_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.
plot_optimization_history is provided by the Optuna MCP Server MCP server (optuna/optuna-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Optuna MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Optuna MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.