Set a spending limit in USD for a specific team member
AI agents use cursor_set_user_spend_limit to commit financial operations through Sage MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly controls financial parameters by setting spending limits in USD for team members. While it caps spending rather than directly moving money, it commits financial policy that governs how much money can be spent, which falls squarely in the Financial category. Misuse could remove spending limits (set to unlimited) or set inappropriate caps, affecting financial exposure.
From the tool's definition Set a spending limit in USD for a specific team member
Documented attack patterns abuse exactly the kind of access cursor_set_user_spend_limit 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_set_user_spend_limit:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_set_user_spend_limit": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to cursor_set_user_spend_limit is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Set a spending limit in USD for a specific team member. It is categorised as a Financial tool in the Sage MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sage MCP server in PolicyLayer and add a rule for cursor_set_user_spend_limit: 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_set_user_spend_limit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cursor_set_user_spend_limit 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_set_user_spend_limit. 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_set_user_spend_limit 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.