New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cursor_set_user_spend_limit

Set a spending limit in USD for a specific team member

SERVERSage MCP SOURCEsagemcp/sagemcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/cursor-set-user-spend-limit.md

What cursor_set_user_spend_limit does on Sage MCP

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.

Why cursor_set_user_spend_limit is rated Critical

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

Questions about cursor_set_user_spend_limit

What does the cursor_set_user_spend_limit tool do? +

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.

How do I enforce a policy on cursor_set_user_spend_limit? +

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.

What risk level is cursor_set_user_spend_limit? +

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.

Can I rate-limit cursor_set_user_spend_limit? +

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.

How do I block cursor_set_user_spend_limit completely? +

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.

What MCP server provides cursor_set_user_spend_limit? +

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.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.