Set a hard spending limit (in dollars) for a specific team member. Use with caution — this will block the user from making requests once the limit is reached.
AI agents use set_spend_limit to create or update resources in Cursor Usage — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cursor Usage environment.
This tool creates or modifies a spending limit configuration for a user, which is reversible (the limit can be changed or removed later). It does not permanently delete data or move money, so it is not Destructive or Financial. However, it has significant operational impact: blocking a user from making requests is a high-severity consequence of misconfiguration.
From the tool's definition 'Set a hard spending limit' and 'will block the user from making requests once the limit is reached' — modifies team member spending configuration with operational side effects.
Attacks that exploit this kind of access
Set a hard spending limit (in dollars) for a specific team member. Use with caution — this will block the user from making requests once the limit is reached. It is categorised as a Write tool in the Cursor Usage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cursor Usage MCP server in PolicyLayer and add a rule for set_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 Cursor Usage. Nothing to install.
set_spend_limit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_spend_limit is provided by the Cursor Usage MCP server (ofershap/cursor-usage). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →