list_qonto_transaction_attachments
AI agents call list_qonto_transaction_attachments 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 lists attachments associated with Qonto transactions, which is a retrieval operation with no side effects. While the server provides access to financial data, listing transaction attachments does not move money, modify records, or trigger external operations—it only queries existing data.
From the tool's definition Tool name 'list_qonto_transaction_attachments' uses the verb 'list', which retrieves or enumerates data. The empty description prevents full certainty, but sibling tools (get_client, get_clients, get_client_invoices, get_qonto_attachment, get_qonto_label,…
Documented attack patterns abuse exactly the kind of access list_qonto_transaction_attachments 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 list_qonto_transaction_attachments:
{
"version": "1",
"default": "deny",
"tools": {
"list_qonto_transaction_attachments": {}
}
}list_qonto_transaction_attachments 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.
list_qonto_transaction_attachments. 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 list_qonto_transaction_attachments: 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.
list_qonto_transaction_attachments 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 list_qonto_transaction_attachments 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 list_qonto_transaction_attachments. 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.
list_qonto_transaction_attachments 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.