List tracking events for a contract within a date range
AI agents call list_tracking_by_date 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 tracking events associated with a contract filtered by date range. It produces no side effects, does not modify data, and does not execute external operations. While it operates within a financial payment protocol context (AP2), the tool itself only reads audit/tracking data, making it a Read operation with low severity.
From the tool's definition The tool name 'list_tracking_by_date' and description 'List tracking events for a contract within a date range' both indicate a retrieval operation. The verb 'list' is a classic Read operation that queries existing data without modification or side effects.
Documented attack patterns abuse exactly the kind of access list_tracking_by_date 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_tracking_by_date:
{
"version": "1",
"default": "deny",
"tools": {
"list_tracking_by_date": {}
}
}list_tracking_by_date 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 tracking events for a contract within a date range. 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_tracking_by_date: 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_tracking_by_date 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_tracking_by_date 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_tracking_by_date. 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_tracking_by_date 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.