Get comprehensive optimization dashboard with performance metrics.
AI agents call get_optimization_dashboard to retrieve information from Ai Analyst without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and displays existing dashboard data and performance metrics without creating, modifying, deleting, or executing any operations. It has no side effects beyond data retrieval, placing it squarely in the Read category with low severity due to minimal risk from misuse.
From the tool's definition Tool name 'get_optimization_dashboard' and description 'Get comprehensive optimization dashboard with performance metrics' indicate a retrieval operation. The verb 'Get' and absence of modification language confirm read-only behavior.
Attacks that exploit this kind of access
Get comprehensive optimization dashboard with performance metrics. It is categorised as a Read tool in the Ai Analyst MCP Server, which means it retrieves data without modifying state.
Register the Ai Analyst MCP server in PolicyLayer and add a rule for get_optimization_dashboard: 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 Ai Analyst. Nothing to install.
get_optimization_dashboard 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_dashboard 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_dashboard. 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_dashboard is provided by the Ai Analyst MCP server (sbdk-dev/local-ai-analyst). 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 →