Retrieves transactions from the Qonto API for a specific bank account.
AI agents call get_qonto_transactions 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.
This tool retrieves historical transaction data without modifying, deleting, or executing financial operations. However, severity is 'high' rather than 'low' because transaction data is sensitive financial information that could expose business operations, client details, and account activity patterns if accessed by a malicious agent.
From the tool's definition Tool name contains 'get_' and description states 'Retrieves transactions', which are read-only operations. No modification, deletion, or financial movement is performed.
Documented attack patterns abuse exactly the kind of access get_qonto_transactions 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_qonto_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_qonto_transactions": {}
}
}get_qonto_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves transactions from the Qonto API for a specific bank account. It is categorised as a Read tool in the Qonto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qonto MCP Server MCP server in PolicyLayer and add a rule for get_qonto_transactions: 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.
get_qonto_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_qonto_transactions 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 get_qonto_transactions. 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.
get_qonto_transactions 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.
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.