List subactivities for a specific Fabric item run with analysis
AI agents call list-fabric-run-subactivities 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 retrieves and displays subactivity details from a completed or running Fabric job execution. It queries metadata about run activities for monitoring and analysis purposes. There are no side effects, data modifications, deletions, code execution, or financial implications. It is a straightforward data retrieval operation, fitting the Read category with low severity due to minimal blast radius if misused.
From the tool's definition Tool name 'list-fabric-run-subactivities' and description 'List subactivities for a specific Fabric item run with analysis' indicate retrieval and querying of run metadata.
Documented attack patterns abuse exactly the kind of access list-fabric-run-subactivities 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 list-fabric-run-subactivities:
{
"version": "1",
"default": "deny",
"tools": {
"list-fabric-run-subactivities": {}
}
}list-fabric-run-subactivities 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.
List subactivities for a specific Fabric item run with analysis. 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 list-fabric-run-subactivities: 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.
list-fabric-run-subactivities 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 list-fabric-run-subactivities 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 list-fabric-run-subactivities. 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.
list-fabric-run-subactivities 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.