Low Risk

get_statements

get_statements

How to control get_statements ↓

AI agents call get_statements to retrieve information from Qonto 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 financial statements from Qonto accounts—a read-only operation with no side effects on data. However, severity is elevated to 'medium' rather than 'low' because financial statements contain sensitive business data (balances, transaction history, potentially client information); unauthorized disclosure could enable fraud or competitive harm, though the tool itself does not move money or cause…

From the tool's definition Tool name 'get_statements' and sibling tool 'download_statement' indicate retrieval of financial statements.

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

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

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

get_statements 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 Qonto 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_statements tool do? +

get_statements. It is categorised as a Read tool in the Qonto MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_statements? +

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

What risk level is get_statements? +

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

Can I rate-limit get_statements? +

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

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

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

Enforce policy on every Qonto MCP Server tool call.

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

Free to start. No card required.

21 Qonto 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.