AI agents call analytics_dashboard to retrieve information from AgentOS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays analytics data without modifying, deleting, or executing any operations. It is a read-only query that returns usage information for display purposes. The blast radius of misuse is minimal—an agent could only access analytics data that may already be available to authorized users.
From the tool's definition Tool name 'analytics_dashboard' combined with description 'Get usage analytics dashboard for today or specified date range' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get usage analytics dashboard for today or specified date range. It is categorised as a Read tool in the AgentOS MCP Server, which means it retrieves data without modifying state.
Register the AgentOS MCP server in PolicyLayer and add a rule for analytics_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 AgentOS. Nothing to install.
analytics_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 analytics_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 analytics_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.
analytics_dashboard is provided by the AgentOS MCP server (netflypsb/agentos). 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 →