Ani

55 tools. 15 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated:

15 can modify or destroy data
40 read-only
55 tools total
Read (40) Write / Execute (9) Destructive / Financial (6)

Destructive tools (anilist_delete_from_list, anilist_drops, anilist_rate) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (anilist_activity, anilist_add_to_list, anilist_batch_update) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (anilist_pick) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Ani. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @ani-mcp
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
Deny destructive operations
anilist_delete_from_list:
  rules:
    - action: deny

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

Rate limit write operations
anilist_activity:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
anilist_airing:
  rules:
    - rate_limit: 60/minute

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

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

Yes. The Ani server exposes 6 destructive tools including anilist_delete_from_list, anilist_drops, anilist_rate. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Ani? +

The Ani server has 8 write tools including anilist_activity, anilist_add_to_list, anilist_batch_update. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Ani MCP server expose? +

55 tools across 4 categories: Destructive, Execute, Read, Write. 40 are read-only. 15 can modify, create, or delete data.

How do I add Intercept to my Ani setup? +

One line change. Instead of running the Ani server directly, prefix it with Intercept: intercept -c io-github-gavmason-ani-mcp.yaml -- npx -y @ani-mcp. Download a pre-built policy from policylayer.com/policies/io-github-gavmason-ani-mcp and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.