Get comprehensive monitoring dashboard for recent runs across workspace
AI agents call monitor-fabric-runs-dashboard to retrieve information from Fabric-Analytics-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves monitoring data about past runs. It does not create, modify, delete, or execute any operations - it only reads and aggregates existing run information for display in a dashboard format. This is a classic Read operation with minimal security risk, suitable for observability and audit purposes.
From the tool's definition The tool 'monitor-fabric-runs-dashboard' retrieves and displays 'comprehensive monitoring dashboard for recent runs' - it performs data querying and presentation without modification, deletion, or execution of operations.
Documented attack patterns abuse exactly the kind of access monitor-fabric-runs-dashboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fabric-Analytics-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for monitor-fabric-runs-dashboard:
{
"version": "1",
"default": "deny",
"tools": {
"monitor-fabric-runs-dashboard": {}
}
}monitor-fabric-runs-dashboard is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get comprehensive monitoring dashboard for recent runs across workspace. It is categorised as a Read tool in the Fabric-Analytics-MCP MCP Server, which means it retrieves data without modifying state.
Register the Fabric-Analytics- MCP server in PolicyLayer and add a rule for monitor-fabric-runs-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 Fabric-Analytics-MCP. Nothing to install.
monitor-fabric-runs-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 monitor-fabric-runs-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 monitor-fabric-runs-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.
monitor-fabric-runs-dashboard is provided by the Fabric-Analytics- MCP server (santhoshravindran7/fabric-analytics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 83 Fabric-Analytics-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
83 Fabric-Analytics-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.