Low Risk

get_account_info

Get detailed information for a linked account.

How to control get_account_info ↓

AI agents call get_account_info to retrieve information from Mono Banking MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves account information without creating, modifying, deleting, or executing operations. It is a read operation. The high severity reflects the sensitivity of banking and personal financial data that could be exposed, even though the tool itself performs no destructive or transactional action.

From the tool's definition Tool name 'get_account_info' and description 'Get detailed information for a linked account' indicate retrieval of account data with no modification.

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

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

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

get_account_info 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 Mono Banking 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_account_info tool do? +

Get detailed information for a linked account. It is categorised as a Read tool in the Mono Banking MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_info? +

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

What risk level is get_account_info? +

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

Can I rate-limit get_account_info? +

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

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

get_account_info is provided by the Mono Banking MCP Server MCP server (sin4ch/mono-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mono Banking MCP Server tool call.

Deterministic rules across all 12 Mono Banking MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 Mono Banking MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.