invoice_received_get
A read tool on the AbraFlexi MCP server.
This record as markdown: /tools/abraflexi/invoice-received-get.md
What invoice_received_get does on AbraFlexi
AI agents call invoice_received_get to retrieve information from AbraFlexi without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why invoice_received_get is rated Low
The 'get' suffix indicates this tool retrieves or queries invoice_received data without modification. No description is available, but the naming convention and presence of sibling read tools (bank_transaction_get, contact_get, evidence_get) on the AbraFlexi server confirm this is a retrieval operation.
From the tool's definition Tool name 'invoice_received_get' uses the verb 'get', which is a standard read operation for retrieving data.
Attacks that exploit this kind of access
The rule that runs invoice_received_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AbraFlexi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invoice_received_get, this is the rule to start with:
invoice_received_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AbraFlexi, apply this rule, and every invoice_received_get call is checked against it from then on.
Questions about invoice_received_get
invoice_received_get is a read tool on the AbraFlexi MCP server. It is categorised as a Read tool in the AbraFlexi MCP Server, which means it retrieves data without modifying state.
Register the AbraFlexi MCP server in PolicyLayer and add a rule for invoice_received_get: 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 AbraFlexi. Nothing to install.
invoice_received_get 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 invoice_received_get 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 invoice_received_get. 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.
invoice_received_get is provided by the AbraFlexi MCP server (abraflexi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AbraFlexi, and thousands of servers like it.
This server
Across the catalogue