set_sponsorship_refill_threshold
(Operator admin-token-gated) Set per-adapter pool refill threshold.
This record as markdown: /tools/network-tenzro-tenzro/set-sponsorship-refill-threshold.md
What set_sponsorship_refill_threshold does on Tenzro Ledger MCP
AI agents use set_sponsorship_refill_threshold to create or update resources in Tenzro Ledger MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenzro Ledger MCP environment.
Why set_sponsorship_refill_threshold is rated Medium
This tool modifies configuration state (refill thresholds) for adapter pools, which is reversible and constitutes a Write operation. However, severity is elevated to 'high' because: (1) it requires admin/operator privileges (token-gated access control), (2) it controls financial or resource-related pool parameters (refill thresholds in a payment/wallet system), and (3) misconfiguration could impact system-wide…
From the tool's definition Tool description states it 'Set[s] per-adapter pool refill threshold' and is '(Operator admin-token-gated)', indicating modification of configuration parameters.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs set_sponsorship_refill_threshold safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_sponsorship_refill_threshold, this is the rule to start with:
set_sponsorship_refill_threshold stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every set_sponsorship_refill_threshold call is checked against it from then on.
Questions about set_sponsorship_refill_threshold
(Operator admin-token-gated) Set per-adapter pool refill threshold. It is categorised as a Write tool in the Tenzro Ledger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for set_sponsorship_refill_threshold: 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.
set_sponsorship_refill_threshold 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_sponsorship_refill_threshold 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_sponsorship_refill_threshold. 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_sponsorship_refill_threshold 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.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue