get_dashboard_stats
AI agents call get_dashboard_stats to retrieve information from Restaurant Backend MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Dashboard statistics are typically read-only aggregations or summaries of existing data. The 'get_' prefix strongly indicates a retrieval operation with no side effects. Without a description, confidence is moderate; however, the context of 'analytics' in the server description and the pattern of other 'get_' tools on the server support a Read classification.
From the tool's definition Tool name 'get_dashboard_stats' indicates a retrieval operation. The description is empty, but the sibling tools on the server (create_menu_item, create_order, create_review, customer_login, get_customer_orders, get_customer_profile, get_filtered_orders,…
Attacks that exploit this kind of access
get_dashboard_stats. It is categorised as a Read tool in the Restaurant Backend MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Restaurant Backend MCP Server MCP server in PolicyLayer and add a rule for get_dashboard_stats: 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 Restaurant Backend MCP Server. Nothing to install.
get_dashboard_stats 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_dashboard_stats 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_dashboard_stats. 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_dashboard_stats is provided by the Restaurant Backend MCP Server MCP server (pasanis/mcp-server). 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 →