Low Risk

getAccounts

List accounts

How to control getAccounts ↓

What getAccounts does on Mcp Upbank

AI agents call getAccounts to retrieve information from Mcp Upbank without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getAccounts needs a policy

This tool retrieves account data without modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius—an AI agent calling this would only fetch existing account information, which is non-sensitive metadata in a banking context where the primary concern is unauthorized writes or transfers.

From the tool's definition Tool name 'getAccounts' and description 'List accounts' indicate a query operation that retrieves account information. Server description confirms 'read-only mode' access to Up Bank API.

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

How to control getAccounts

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAccounts": {}
  }
}

getAccounts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Upbank — 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getAccounts

What does the getAccounts tool do? +

List accounts. It is categorised as a Read tool in the Mcp Upbank MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAccounts? +

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

What risk level is getAccounts? +

getAccounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getAccounts? +

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

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

getAccounts is provided by the Mcp Upbank MCP server (sirmews/mcp-upbank). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Upbank tool call.

Start from Mcp Upbank, 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.

13 Mcp Upbank 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.