Medium Risk

anilist_batch_update

Apply a bulk action to multiple list entries matching a filter. Use when the user wants to move all low-scored titles to Dropped, add all planning titles to current, or bulk-change statuses. Defaults to dry-run mode (preview only). Requires ANILIST_TOKEN.

High parameter count (12 properties)

Part of the Ani MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ani-mcp Write Risk 2/5

AI agents use anilist_batch_update to create or modify resources in Ani. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call anilist_batch_update repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ani.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-gavmason-ani-mcp.yaml
tools:
  anilist_batch_update:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Ani policy for all 55 tools.

Tool Name anilist_batch_update
Category Write
MCP Server Ani MCP Server
Risk Level Medium

View all 55 tools →

Agents calling write-class tools like anilist_batch_update have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the anilist_batch_update tool do? +

Apply a bulk action to multiple list entries matching a filter. Use when the user wants to move all low-scored titles to Dropped, add all planning titles to current, or bulk-change statuses. Defaults to dry-run mode (preview only). Requires ANILIST_TOKEN.. It is categorised as a Write tool in the Ani MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on anilist_batch_update? +

Add a rule in your Intercept YAML policy under the tools section for anilist_batch_update. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ani MCP server.

What risk level is anilist_batch_update? +

anilist_batch_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit anilist_batch_update? +

Yes. Add a rate_limit block to the anilist_batch_update rule in your Intercept 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.

How do I block anilist_batch_update completely? +

Set action: deny in the Intercept policy for anilist_batch_update. 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.

What MCP server provides anilist_batch_update? +

anilist_batch_update is provided by the Ani MCP server (ani-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ani

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.