set_budget_limits
Patch your per-account AI-spend limits — the two daily circuit breakers and the four per-tree run knobs. Only the fields you pass are changed; anything you omit keeps its stored value. Pass null for a field to clear that override so it inherits from the platform default. Values are clamped server...
This record as markdown: /tools/io-github-proagentstore-platform/set-budget-limits.md
What set_budget_limits does on ProAgentStore
AI agents use set_budget_limits to commit financial operations through ProAgentStore, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why set_budget_limits is rated Critical
Modifies financial spend limits controlling AI budget, directly affecting financial obligations.
From the tool's definition patch per-account AI-spend limits, daily circuit breakers, budget limits
Attacks that exploit this kind of access
The rule that runs set_budget_limits safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_budget_limits, this is the rule to start with:
Any call to set_budget_limits is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every set_budget_limits call is checked against it from then on.
Questions about set_budget_limits
Patch your per-account AI-spend limits — the two daily circuit breakers and the four per-tree run knobs. Only the fields you pass are changed; anything you omit keeps its stored value. Pass null for a field to clear that override so it inherits from the platform default. Values are clamped server-side to the platform maximum ($10 000 / 100B tokens per 24h). Returns the re-resolved effective limits after the write — same shape as get_budget_limits. Read get_budget_limits first to see the current state. It is categorised as a Financial tool in the ProAgentStore MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for set_budget_limits: 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 ProAgentStore. Nothing to install.
set_budget_limits 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 set_budget_limits 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_budget_limits. 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_budget_limits is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue