add_batch · Nesift MCP: Risk & Policy

WHAT IT DOES

What add_batch does on Nesift

AI agents use add_batch to create or update resources in Nesift — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nesift environment.

WHY IT NEEDS A POLICY

Why add_batch needs a policy

This tool adds new data (web pages) to the system's index. While it does not delete or overwrite existing data (which would be Destructive), and does not execute arbitrary code (which would be Execute), it does perform a Write operation — ingesting and indexing URLs modifies the state of the semantic search index.

From the tool's definition 'Ingest multiple URLs in parallel' — the tool writes/indexes new web content into the local semantic search system, creating persistent records that modify the indexed data store.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_batch Rate-limited

add_batch stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_batch": {
      "limits": [
        {
          "counter": "add_batch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nesift, so you can run agents against it safely.

FAQ

Questions about add_batch

What does the add_batch tool do? +

Ingest multiple URLs in parallel. It is categorised as a Write tool in the Nesift MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_batch? +

Register the Nesift MCP server in PolicyLayer and add a rule for add_batch: 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 Nesift. Nothing to install.

What risk level is add_batch? +

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

Can I rate-limit add_batch? +

Yes. Add a rate_limit block to the add_batch 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.

How do I block add_batch completely? +

Set action: deny in the PolicyLayer policy for add_batch. 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 add_batch? +

add_batch is provided by the Nesift MCP server (scottgl9/nesift). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.