setup_metered_billing

THE RISK

Critical Risk

Why setup_metered_billing needs a policy

This tool commits a financial obligation by creating a recurring billing subscription. An AI agent misusing this tool could establish a subscription that results in ongoing charges, making it a Financial category risk. The severity is critical because it creates an open-ended financial commitment that scales with usage and recurs monthly, with potentially unbounded cost exposure.

From the tool's definition Set up pay-per-call billing. Creates a subscription that charges $0.002 per API call at end of month.

Documented attack patterns abuse exactly the kind of access setup_metered_billing gives an agent:

POLICY

How to control setup_metered_billing

PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for setup_metered_billing:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_metered_billing": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to setup_metered_billing is blocked until a human approves it. The rest of the server keeps working.

Create a free account and register APIClaw — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More APIClaw tools

Execute call_api Execute a callable API through APIClaw Execute capability Run a job-to-be-done by capability name (currency_convert, web_search, tts, transcribe, sc Execute start_mission Start a Control Plane mission — a structured, observable orchestration that runs on APICla Execute resume_chain Resume a paused or partially-executed chain by id. Write verify_code Verify the 6-digit code sent to your email after register_owner. This completes registrati Write register_owner LEGACY auth path (kept for back-compat). The canonical agent-native flow is Write remind_owner Send a reminder email to verify workspace ownership (if verification is pending). Read apiclaw_help Get help and a tour of APIClaw

All 24 APIClaw tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in APIClaw → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about setup_metered_billing

What does the setup_metered_billing tool do? +

Set up pay-per-call billing. Creates a subscription that charges $0.002 per API call at end of month. It is categorised as a Financial tool in the APIClaw MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on setup_metered_billing? +

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

What risk level is setup_metered_billing? +

setup_metered_billing is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit setup_metered_billing? +

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

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

setup_metered_billing is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every APIClaw tool call.

Start from APIClaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →