List financial events scoped to a single order (shipment, refund, service fee, adjustment). Cleaner than list_financial_events when reconciling one order.
AI agents call list_financial_events_by_order 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.
This tool retrieves and queries existing financial event records (shipment, refund, service fee, adjustment) without creating, modifying, deleting, or moving money. It is a read operation for audit and reconciliation purposes, with no side effects. While it accesses financial data, it does not commit financial obligations or trigger payments, so it does not qualify as Financial category.
From the tool's definition Tool name 'list_financial_events_by_order' and description 'List financial events scoped to a single order' — the verb 'List' and action 'scoped to' indicate read-only retrieval of historical financial transaction data for a single order.
Documented attack patterns abuse exactly the kind of access list_financial_events_by_order 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_financial_events_by_order:
{
"version": "1",
"default": "deny",
"tools": {
"list_financial_events_by_order": {}
}
} list_financial_events_by_order 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 financial events scoped to a single order (shipment, refund, service fee, adjustment). Cleaner than list_financial_events when reconciling one order. 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_financial_events_by_order: 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_financial_events_by_order 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_financial_events_by_order 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_financial_events_by_order. 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_financial_events_by_order 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.