list_payments
List payment history for this account.
This record as markdown: /tools/dev-aic0rt3x-memory-mcp/list-payments.md
What list_payments does on AI Cortex Storage
AI agents call list_payments to retrieve information from AI Cortex Storage 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 |
|---|---|---|---|
limit | integer | — | Max results (default 50, max 100) |
offset | integer | — | Pagination offset (default 0) |
Parameters from the server's own tool schema.
Why list_payments is rated Low
This tool retrieves payment history records, which is a Read operation (queries data with no side effects). However, severity is elevated to 'medium' rather than 'low' because payment history data is sensitive financial information that could reveal transaction patterns, amounts, and account details if misused by an AI agent—though the tool itself does not execute financial transactions or cause destructive changes.
From the tool's definition Tool name 'list_payments' and description 'List payment history for this account' indicate a read-only query operation that retrieves historical payment data without modifying or executing transactions.
Attacks that exploit this kind of access
The rule that runs list_payments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI Cortex Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_payments, this is the rule to start with:
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 AI Cortex Storage, apply this rule, and every list_payments call is checked against it from then on.
Questions about list_payments
List payment history for this account. It is categorised as a Read tool in the AI Cortex Storage MCP Server, which means it retrieves data without modifying state.
list_payments accepts 2 parameters: limit, offset. The full parameter table on this page comes from the server's own tool schema.
Register the AI Cortex Storage MCP server in PolicyLayer and add a rule for 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 AI Cortex Storage. Nothing to install.
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 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 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.
list_payments is provided by the AI Cortex Storage MCP server (https://memory.aic0rt3x.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI Cortex Storage, and thousands of servers like it.
This server
Across the catalogue