AI agents call get_qonto_attachment 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.
The 'get_' prefix and attachment retrieval pattern indicate a read-only query operation. However, severity is elevated to 'high' rather than 'low' because attachments in a financial context (likely invoices, statements, receipts, contracts) may contain sensitive business or transaction data. Despite empty description, the tool's purpose aligns with data retrieval, not modification or execution.
From the tool's definition Tool name 'get_qonto_attachment' indicates data retrieval. Server context shows financial data access (Qonto banking platform). Sibling tools (get_client, get_qonto_transaction, etc.) are all Read operations.
Documented attack patterns abuse exactly the kind of access get_qonto_attachment 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_attachment:
{
"version": "1",
"default": "deny",
"tools": {
"get_qonto_attachment": {}
}
}get_qonto_attachment 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.
get_qonto_attachment. 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_attachment: 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_attachment 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_attachment 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_attachment. 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_attachment 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.