indexfoundry_normalize_enrich · IndexFoundry MCP

WHAT IT DOES

What indexfoundry_normalize_enrich does on IndexFoundry MCP

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

WHY IT NEEDS A POLICY

Why indexfoundry_normalize_enrich needs a policy

The tool modifies existing data chunks by adding/enriching them with metadata (language, tags, classifications, taxonomy). This is a reversible write/update operation on stored chunk data. It does not delete data, execute code, or involve financial transactions. Severity is medium because enrichment could alter downstream RAG retrieval behavior and pipeline outputs if misapplied.

From the tool's definition Enrich chunks with metadata: language detection, regex-based tagging, section classification, and taxonomy mapping

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indexfoundry_normalize_enrich Rate-limited

indexfoundry_normalize_enrich 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": {
    "indexfoundry_normalize_enrich": {
      "limits": [
        {
          "counter": "indexfoundry_normalize_enrich_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 IndexFoundry MCP, so you can run agents against it safely.

FAQ

Questions about indexfoundry_normalize_enrich

What does the indexfoundry_normalize_enrich tool do? +

Enrich chunks with metadata: language detection, regex-based tagging, section classification, and taxonomy mapping. It is categorised as a Write tool in the IndexFoundry MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on indexfoundry_normalize_enrich? +

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

What risk level is indexfoundry_normalize_enrich? +

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

Can I rate-limit indexfoundry_normalize_enrich? +

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

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

indexfoundry_normalize_enrich is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.