add_page · Nesift MCP: Risk & Policy

WHAT IT DOES

What add_page does on Nesift

AI agents use add_page 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_page needs a policy

The tool fetches and processes external content, then stores it in the semantic search index. This is a Write operation because it creates/adds indexed data structures. Severity is medium because: (1) the modification is reversible (clear tool exists), (2) blast radius is limited to the local index, and (3) an agent fetching and indexing malicious content could pollute the index or consume resources, but cannot…

From the tool's definition Tool description states it will 'Fetch a URL, extract clean text, chunk by heading, and index it into' — the indexing operation modifies the internal search database, creating new indexed records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_page Rate-limited

add_page 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_page": {
      "limits": [
        {
          "counter": "add_page_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_page

What does the add_page tool do? +

Fetch a URL, extract clean text, chunk by heading, and index it into. 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_page? +

Register the Nesift MCP server in PolicyLayer and add a rule for add_page: 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_page? +

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

Can I rate-limit add_page? +

Yes. Add a rate_limit block to the add_page 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_page completely? +

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

add_page 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.