get_dashboard_kpis
Workspace-wide aggregate stats — execution counts, email/LinkedIn rates, completion percentage.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-dashboard-kpis.md
What get_dashboard_kpis does on Max MCP Server
AI agents call get_dashboard_kpis to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dashboard_kpis is rated Low
The tool retrieves and queries aggregate statistics and KPI data from a workspace dashboard. It performs no data modification, deletion, or execution of external operations. This is a straightforward read operation with minimal security risk, as it only exposes aggregated metrics without the ability to modify settings, delete data, or trigger actions.
From the tool's definition Tool description states it fetches 'Workspace-wide aggregate stats — execution counts, email/LinkedIn rates, completion percentage.' These are retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_dashboard_kpis safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dashboard_kpis, this is the rule to start with:
get_dashboard_kpis is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every get_dashboard_kpis call is checked against it from then on.
Questions about get_dashboard_kpis
Workspace-wide aggregate stats — execution counts, email/LinkedIn rates, completion percentage. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for get_dashboard_kpis: 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 Max MCP Server. Nothing to install.
get_dashboard_kpis 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_kpis 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_kpis. 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_kpis is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue