AI agents call get_requests 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.
Despite the empty description lowering confidence slightly, the naming pattern ('get_') and server context (financial data access) strongly indicate this is a retrieval/query tool with no side effects.
From the tool's definition Tool name 'get_requests' with empty description on a Qonto financial server alongside other 'get_' tools (get_client, get_clients, get_qonto_attachment, etc.) that retrieve financial data.
Documented attack patterns abuse exactly the kind of access get_requests 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_requests:
{
"version": "1",
"default": "deny",
"tools": {
"get_requests": {}
}
}get_requests 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_requests. 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_requests: 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_requests 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_requests 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_requests. 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_requests 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.