neuron_ingest_knowledge

Ingest content into a knowledge base. Supports deduplication via externalId and optional LLM processing (summarize, extract_facts, or custom instruction).

SERVERNeuron SOURCEneuron-mcp-server
Medium RISK CLASS
Category Write
Parameters 83 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-ingest-knowledge.md

What neuron_ingest_knowledge does on Neuron

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

ParameterTypeRequiredDescription
title string Yes Title for the knowledge entry
folder string Folder: 'general', 'skills', 'contexts', 'documents', or 'faqs' (default: general)
source string Source type (default: mcp)
content string Yes Content to ingest
sourceUrl string Source URL for reference
externalId string Unique external ID for deduplication (e.g. file path, URL)
processing object Optional LLM processing before storage
knowledgeBaseId string Yes Knowledge base ID to ingest into

Parameters from the server's own tool schema.

Why neuron_ingest_knowledge is rated Medium

The tool creates or modifies knowledge base content by ingesting new data and optionally processing it via LLM. This is a reversible write operation (content can be removed or replaced later), not a read query, code execution, or destructive deletion.

From the tool's definition Tool description states 'Ingest content into a knowledge base' — a create/modify operation that adds or updates data. Supports optional LLM processing (summarize, extract_facts, or custom instruction), which are transformative operations on ingested content.

Risk signalsAccepts file system path (folder) · Accepts raw HTML/template content (content) · High parameter count (10 properties)

Questions about neuron_ingest_knowledge

What does the neuron_ingest_knowledge tool do? +

Ingest content into a knowledge base. Supports deduplication via externalId and optional LLM processing (summarize, extract_facts, or custom instruction). It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does neuron_ingest_knowledge accept? +

neuron_ingest_knowledge accepts 8 parameters: title, folder, source, content, sourceUrl, externalId, processing, knowledgeBaseId. Required: title, content, knowledgeBaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_ingest_knowledge? +

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

What risk level is neuron_ingest_knowledge? +

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

Can I rate-limit neuron_ingest_knowledge? +

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

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

neuron_ingest_knowledge is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Neuron, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Neuron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.