Abacus

22 tools. 10 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

10 can modify or destroy data
12 read-only
22 tools total

Community server · catalogue entry verified 12/06/2026

How to control Abacus ↓

What Abacus exposes to your agents

Read (12) Write / Execute (9) Destructive / Financial (1)
Critical Risk

The most dangerous Abacus tools

10 of Abacus's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Abacus

PolicyLayer is an MCP gateway — it sits between your AI agents and Abacus, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "cancel_calculation": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "run_phonon_preparation": {
    "limits": [
      {
        "counter": "run_phonon_preparation_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "calculate_charge_density": {
    "limits": [
      {
        "counter": "calculate_charge_density_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Abacus — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON ABACUS →

Free to start. No card required.

All 22 Abacus tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Abacus

Can an AI agent delete data through the Abacus MCP server? +

Yes. The Abacus server exposes 1 destructive tools including cancel_calculation. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Abacus? +

The Abacus server has 3 write tools including run_phonon_preparation, convert_structure, create_structure. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Abacus.

How many tools does the Abacus MCP server expose? +

22 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 12 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on Abacus? +

Register the Abacus MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Abacus tool call.

Deterministic rules across all 22 Abacus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

22 Abacus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.