This record as markdown: /tools/io-github-portel-dev-ncp/list-payments.md
What list_payments does on Ncp
AI agents call list_payments to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_payments is rated Low
This tool retrieves and displays payment records. It performs a read-only query of historical data with no ability to create, modify, delete, or execute transactions. While it accesses financial data, it does not move money or create financial obligations—it merely queries past payment information.
From the tool's definition Tool name is 'list_payments' and description states 'List payment history'. The verb 'list' and 'history' indicate retrieval of existing data without modification or financial transaction.
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 Ncp, 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 Ncp, apply this rule, and every list_payments call is checked against it from then on.
Questions about list_payments
List payment history. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue