set_low_balance_alert · Run402 MCP: Risk & Policy

WHAT IT DOES

What set_low_balance_alert does on Run402

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

WHY IT NEEDS A POLICY

Why set_low_balance_alert needs a policy

This tool modifies alert settings for a financial account (KMS signer balance monitoring), making it a Write operation. It does not move funds (not Financial), execute arbitrary code (not Execute), or delete data (not Destructive). However, misconfiguration could suppress critical low-balance warnings, risking operational disruption or undetected insufficient funds for infrastructure payments.

From the tool's definition Tool name 'set_low_balance_alert' and description 'Set the low-balance threshold' indicate modification of alert configuration parameters. Description states 'Email alerts fire when the signer' (incomplete but suggests alert triggering behavior).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_low_balance_alert Rate-limited

set_low_balance_alert 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_low_balance_alert": {
      "limits": [
        {
          "counter": "set_low_balance_alert_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Run402, so you can run agents against it safely.

FAQ

Questions about set_low_balance_alert

What does the set_low_balance_alert tool do? +

Set the low-balance threshold (in wei) for a KMS signer. Email alerts fire when the signer. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_low_balance_alert? +

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

What risk level is set_low_balance_alert? +

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

Can I rate-limit set_low_balance_alert? +

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

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

set_low_balance_alert is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.