Medium Risk

create_bank_account

Új bankszámla hozzáadása

How to control create_bank_account ↓

What create_bank_account does on Billingo MCP Server

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

Medium Risk

Why create_bank_account needs a policy

This tool creates (adds) a new bank account record, which is a reversible modification of data in the invoicing system. While it involves financial context (bank account), the tool itself does not move money, process payments, or commit financial obligations—it only records account information. This qualifies as Write rather than Financial.

From the tool's definition Tool name 'create_bank_account' and description 'Új bankszámla hozzáadása' (Add new bank account) indicate creation of a new financial account record in the Billingo invoicing system.

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

How to control create_bank_account

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_bank_account": {
      "limits": [
        {
          "counter": "create_bank_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Billingo MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_bank_account

What does the create_bank_account tool do? +

Új bankszámla hozzáadása. It is categorised as a Write tool in the Billingo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_bank_account? +

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

What risk level is create_bank_account? +

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

Can I rate-limit create_bank_account? +

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

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

create_bank_account is provided by the Billingo MCP Server MCP server (szotasz/billingo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Billingo MCP Server tool call.

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

Free to start. No card required.

42 Billingo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.