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

update_spending_limit

Update the spending limit for an access key on a specific token.

SERVERTempo SOURCEarome3/tempo-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/update-spending-limit.md

What update_spending_limit does on Tempo

AI agents use update_spending_limit to create or update resources in Tempo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempo environment.

Why update_spending_limit is rated Medium

This tool modifies an existing spending limit (a reversible Write operation) rather than executing a payment or irreversibly deleting data. However, severity is high because misconfiguring spending limits on a blockchain stablecoin payment system could enable unauthorized transactions up to the new limit, creating significant financial exposure.

From the tool's definition Tool description states 'Update the spending limit' — this modifies access control parameters for a token, which is a reversible change to system configuration.

Questions about update_spending_limit

What does the update_spending_limit tool do? +

Update the spending limit for an access key on a specific token. It is categorised as a Write tool in the Tempo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_spending_limit? +

Register the Tempo MCP server in PolicyLayer and add a rule for update_spending_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 Tempo. Nothing to install.

What risk level is update_spending_limit? +

update_spending_limit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_spending_limit? +

Yes. Add a rate_limit block to the update_spending_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 update_spending_limit completely? +

Set action: deny in the PolicyLayer policy for update_spending_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 update_spending_limit? +

update_spending_limit is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tempo, 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 Tempo'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.