Get dashboard statistics and key metrics
AI agents call passgage_get_dashboard_stats to retrieve information from Passgage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing dashboard data (statistics and metrics). It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal — an agent could only access workforce metrics already visible to authenticated users, posing no risk of data loss, financial harm, or unauthorized changes.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get dashboard statistics and key metrics' — both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get dashboard statistics and key metrics. It is categorised as a Read tool in the Passgage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Passgage MCP Server MCP server in PolicyLayer and add a rule for passgage_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 Passgage MCP Server. Nothing to install.
passgage_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 passgage_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 passgage_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.
passgage_get_dashboard_stats is provided by the Passgage MCP Server MCP server (passgage/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 →