Get the current spending limits and usage for a wallet.
AI agents call get_spending_limits to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about spending limits and usage—a passive query with no side effects. It does not execute transactions, modify limits, move funds, or trigger external operations. Despite the financial context (wallet spending), the action itself is purely informational, matching the Read category. Severity is low because querying spending limit data poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_spending_limits' and description 'Get the current spending limits and usage for a wallet' indicate a read-only query operation that retrieves wallet configuration data without modifying or executing any financial transactions.
Attacks that exploit this kind of access
Get the current spending limits and usage for a wallet. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for get_spending_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 Tenzro Ledger MCP. Nothing to install.
get_spending_limits is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_spending_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 get_spending_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.
get_spending_limits is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). 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 →