Build an MCP telemetry dashboard to surface high-value tools, failing/slow tools, and prioritized improvement opportunities.
AI agents call mcp_metrics_dashboard to retrieve information from MCP SAPUI5 Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and aggregates telemetry/metrics data to produce a dashboard view. It surfaces existing data (tool usage, failure rates, performance) without modifying, executing, or deleting anything. The blast radius of misuse is low since it only reads observability data.
From the tool's definition 'Build an MCP telemetry dashboard to surface high-value tools, failing/slow tools, and prioritized improvement opportunities'
Attacks that exploit this kind of access
Build an MCP telemetry dashboard to surface high-value tools, failing/slow tools, and prioritized improvement opportunities. It is categorised as a Read tool in the MCP SAPUI5 Server MCP Server, which means it retrieves data without modifying state.
Register the MCP SAPUI5 Server MCP server in PolicyLayer and add a rule for mcp_metrics_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 MCP SAPUI5 Server. Nothing to install.
mcp_metrics_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 mcp_metrics_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 mcp_metrics_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.
mcp_metrics_dashboard is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). 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 →