List recently submitted calculation tasks.
AI agents call list_recent_calculations to retrieve information from Abacus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely lists or retrieves historical data about calculations that have already been submitted. It does not modify, execute, delete, or move any data or money. The action is purely informational and read-only, matching the 'Read' category definition of retrieving or querying data without side effects.
From the tool's definition Tool name 'list_recent_calculations' and description 'List recently submitted calculation tasks' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_recent_calculations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Abacus, and nothing reaches the server without passing your rules. This is the rule we recommend for list_recent_calculations:
{
"version": "1",
"default": "deny",
"tools": {
"list_recent_calculations": {}
}
}list_recent_calculations 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 recently submitted calculation tasks. It is categorised as a Read tool in the Abacus MCP Server, which means it retrieves data without modifying state.
Register the Abacus MCP server in PolicyLayer and add a rule for list_recent_calculations: 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 Abacus. Nothing to install.
list_recent_calculations 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_recent_calculations 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_recent_calculations. 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_recent_calculations is provided by the Abacus MCP server (phelanshao/abacus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Abacus, 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.
22 Abacus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.