get_escalation_dashboard
Dashboard eskalacji: podsumowanie pending escalations, najczęstsze przyczyny, avg czas reakcji.
This record as markdown: /tools/mapi-agent-memory/get-escalation-dashboard.md
What get_escalation_dashboard does on Mapi Agent Memory
AI agents call get_escalation_dashboard to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_escalation_dashboard is rated Low
This tool retrieves and displays dashboard information about escalations—pending items, common reasons, and response time metrics. No data is modified, deleted, or financial operations are performed. It is purely informational/analytical in nature, making it a Read category tool with low severity since misuse would only expose summary information about escalation patterns.
From the tool's definition Tool name 'get_escalation_dashboard' and description indicate retrieval of summary data: 'podsumowanie pending escalations' (summary of pending escalations), 'najczęstsze przyczyny' (most frequent causes), 'avg czas reakcji' (average response time).
Attacks that exploit this kind of access
The rule that runs get_escalation_dashboard safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_escalation_dashboard, this is the rule to start with:
get_escalation_dashboard 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 Mapi Agent Memory, apply this rule, and every get_escalation_dashboard call is checked against it from then on.
Questions about get_escalation_dashboard
Dashboard eskalacji: podsumowanie pending escalations, najczęstsze przyczyny, avg czas reakcji. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for get_escalation_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 Mapi Agent Memory. Nothing to install.
get_escalation_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_escalation_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_escalation_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_escalation_dashboard is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue