List charges, newest first. Supports cursor pagination via starting_after / ending_before.
AI agents call list_charges to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries charge data in paginated format. It has no side effects—it does not create, modify, delete, or execute operations. While the data retrieved may be financially sensitive (charges are payment-related), the tool itself only reads and does not move money or create financial obligations. The pagination parameters are read-only control mechanisms.
From the tool's definition Tool name 'list_charges' combined with description 'List charges, newest first. Supports cursor pagination via starting_after / ending_before' indicates a data retrieval operation with no modification or deletion capabilities.
Documented attack patterns abuse exactly the kind of access list_charges gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for list_charges:
{
"version": "1",
"default": "deny",
"tools": {
"list_charges": {}
}
} list_charges 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.
List charges, newest first. Supports cursor pagination via starting_after / ending_before. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for list_charges: 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 Mcp Ap2. Nothing to install.
list_charges 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_charges 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_charges. 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_charges is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.