payment_get_list_payments
Lists payments a company has received, newest first, each with the invoice it was applied to. Read-only and paginated. Use this to answer "what has come in" or to reconcile an invoice against what was actually collected.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/payment-get-list-payments.md
What payment_get_list_payments does on Lovie Company Formation MCP
AI agents call payment_get_list_payments to retrieve information from Lovie Company Formation MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
filter | object | — | |
pageSize | integer | — | |
pageToken | string | — |
Parameters from the server's own tool schema.
Why payment_get_list_payments is rated Low
Even though payment_get_list_payments only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs payment_get_list_payments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lovie Company Formation MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For payment_get_list_payments, this is the rule to start with:
payment_get_list_payments 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 Lovie Company Formation MCP, apply this rule, and every payment_get_list_payments call is checked against it from then on.
Questions about payment_get_list_payments
Lists payments a company has received, newest first, each with the invoice it was applied to. Read-only and paginated. Use this to answer "what has come in" or to reconcile an invoice against what was actually collected. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.
payment_get_list_payments accepts 3 parameters: filter, pageSize, pageToken. The full parameter table on this page comes from the server's own tool schema.
Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for payment_get_list_payments: 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 Lovie Company Formation MCP. Nothing to install.
payment_get_list_payments 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 payment_get_list_payments 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 payment_get_list_payments. 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.
payment_get_list_payments is provided by the Lovie Company Formation MCP server (lovie). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lovie Company Formation, and thousands of servers like it.
This server
Across the catalogue