ingest_url · Rag MCP: Risk & Policy

WHAT IT DOES

What ingest_url does on Rag

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

WHY IT NEEDS A POLICY

Why ingest_url needs a policy

This tool fetches external content from a URL and writes/stores it into the knowledge base. It creates new data in the system (ingestion), which is a Write operation. The external fetch could introduce uncontrolled content, raising the severity to medium, but it is reversible (documents can be deleted).

From the tool's definition Fetch a webpage and ingest its content

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_url Rate-limited

ingest_url 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": {
    "ingest_url": {
      "limits": [
        {
          "counter": "ingest_url_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 Rag, so you can run agents against it safely.

FAQ

Questions about ingest_url

What does the ingest_url tool do? +

Fetch a webpage and ingest its content. It is categorised as a Write tool in the Rag MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ingest_url? +

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

What risk level is ingest_url? +

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

Can I rate-limit ingest_url? +

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

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

ingest_url is provided by the Rag MCP server (mrankitvish/rag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.