Low Risk

retry_with_payment

Retry a paid query after paying the Lightning invoice. Provide the payment_hash from the original response.

Part of the Maximum Sats MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call retry_with_payment to retrieve information from Maximum Sats without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though retry_with_payment only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

maximumsats-maximumsats.yaml
tools:
  retry_with_payment:
    rules:
      - action: allow

See the full Maximum Sats policy for all 5 tools.

Tool Name retry_with_payment
Category Read
Risk Level Low

Agents calling read-class tools like retry_with_payment have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the retry_with_payment tool do? +

Retry a paid query after paying the Lightning invoice. Provide the payment_hash from the original response.. It is categorised as a Read tool in the Maximum Sats MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retry_with_payment? +

Add a rule in your Intercept YAML policy under the tools section for retry_with_payment. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Maximum Sats MCP server.

What risk level is retry_with_payment? +

retry_with_payment is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit retry_with_payment? +

Yes. Add a rate_limit block to the retry_with_payment rule in your Intercept 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 retry_with_payment completely? +

Set action: deny in the Intercept policy for retry_with_payment. 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 retry_with_payment? +

retry_with_payment is provided by the Maximum Sats MCP server (maximumsats/maximumsats). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Maximum Sats

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.