AI agents call fabric_synapse_compute_spend 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.
Given the context of sibling tools that are clearly analytical (analyze-*), this tool most likely retrieves or queries compute spend information from Microsoft Fabric/Synapse, which is a Read operation. No evidence suggests data modification, deletion, execution, or financial transactions. Confidence is moderate due to the empty description, which limits certainty about side effects or actual behavior.
From the tool's definition Tool name 'fabric_synapse_compute_spend' suggests querying or analyzing compute spend data. The empty description prevents definitive classification, but the naming pattern (prefixed with 'analyze-' siblings like 'analyze-fabric-model',…
Documented attack patterns abuse exactly the kind of access fabric_synapse_compute_spend 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 fabric_synapse_compute_spend:
{
"version": "1",
"default": "deny",
"tools": {
"fabric_synapse_compute_spend": {}
}
}fabric_synapse_compute_spend 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.
fabric_synapse_compute_spend. 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 fabric_synapse_compute_spend: 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.
fabric_synapse_compute_spend 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 fabric_synapse_compute_spend 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 fabric_synapse_compute_spend. 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.
fabric_synapse_compute_spend 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.