AI agents call cursor_get_spending to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this tool accesses financial data (spending information), it performs a read-only query operation with no side effects—it retrieves but does not move money, process payments, create subscriptions, or commit financial obligations. This makes it Read rather than Financial.
From the tool's definition Tool name 'cursor_get_spending' and description 'Get team spending breakdown for a date range' indicate a retrieval/query operation that reads existing financial data without modification, deletion, or transaction execution.
Documented attack patterns abuse exactly the kind of access cursor_get_spending gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cursor_get_spending:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_get_spending": {}
}
}cursor_get_spending 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 team spending breakdown for a date range. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for cursor_get_spending: 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 Sage MCP. Nothing to install.
cursor_get_spending 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 cursor_get_spending 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 cursor_get_spending. 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.
cursor_get_spending is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.