topup_billing_wallet
Initiate a top-up for 81 Pay corporate wallet. REQUIRES HUMAN CONFIRMATION.
This record as markdown: /tools/81pass-mcp-server/topup-billing-wallet.md
What topup_billing_wallet does on 81pass
AI agents use topup_billing_wallet to create or update resources in 81pass, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 81pass environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | Yes | Amount to top-up |
currency | string | Yes | Currency (USD or COP) |
confirmationToken | string | — | Confirmation token from step 1 |
Parameters from the server's own tool schema.
Why topup_billing_wallet is rated Medium
An AI agent can call topup_billing_wallet faster than any human can review: one bad instruction and it creates or modifies resources in 81pass by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs topup_billing_wallet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 81pass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For topup_billing_wallet, this is the rule to start with:
topup_billing_wallet 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 81pass, apply this rule, and every topup_billing_wallet call is checked against it from then on.
Questions about topup_billing_wallet
Initiate a top-up for 81 Pay corporate wallet. REQUIRES HUMAN CONFIRMATION. It is categorised as a Write tool in the 81pass MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
topup_billing_wallet accepts 3 parameters: amount, currency, confirmationToken. Required: amount, currency. The full parameter table on this page comes from the server's own tool schema.
Register the 81pass MCP server in PolicyLayer and add a rule for topup_billing_wallet: 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 81pass. Nothing to install.
topup_billing_wallet 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 topup_billing_wallet 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 topup_billing_wallet. 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.
topup_billing_wallet is provided by the 81pass MCP server (@81pass/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 81pass, and thousands of servers like it.
This server
Across the catalogue