update_lightning_static_charges · Zbd MCP: Risk & Policy

WHAT IT DOES

What update_lightning_static_charges does on Zbd

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

WHY IT NEEDS A POLICY

Why update_lightning_static_charges needs a policy

This tool modifies (rather than creates or destroys) the configuration of Lightning static charges, which are financial instruments in a cryptocurrency/payments context. The modification is reversible.

From the tool's definition Tool name 'update_lightning_static_charges' and description 'Change the configuration of a Static Charge QR code' indicate modification of existing configuration data. The verb 'Change' and 'update' in the name confirm Write-class behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_lightning_static_charges Rate-limited

update_lightning_static_charges 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": {
    "update_lightning_static_charges": {
      "limits": [
        {
          "counter": "update_lightning_static_charges_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 Zbd, so you can run agents against it safely.

FAQ

Questions about update_lightning_static_charges

What does the update_lightning_static_charges tool do? +

Change the configuration of a Static Charge QR code. It is categorised as a Write tool in the Zbd 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_lightning_static_charges? +

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

What risk level is update_lightning_static_charges? +

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

Can I rate-limit update_lightning_static_charges? +

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

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

update_lightning_static_charges is provided by the Zbd MCP server (zebedeeio/zbd-payments-typescript-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

update_lightning_static_charges is one line of Zbd's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →