knowledge_base
The knowledge base that grounds the AI surfaces — read it, or add a document. Adding is a WRITE, and it changes what every grounded surface says. A wrong document here is repeated confidently everywhere, so add deliberately.
This record as markdown: /tools/io-github-0nork-0nmcp/knowledge-base.md
What knowledge_base does on 0nmcp
AI agents use knowledge_base to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why knowledge_base is rated Medium
An AI agent can call knowledge_base faster than any human can review: one bad instruction and it creates or modifies resources in 0nmcp by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs knowledge_base safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For knowledge_base, this is the rule to start with:
knowledge_base 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every knowledge_base call is checked against it from then on.
Questions about knowledge_base
The knowledge base that grounds the AI surfaces — read it, or add a document. Adding is a WRITE, and it changes what every grounded surface says. A wrong document here is repeated confidently everywhere, so add deliberately. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for knowledge_base: 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 0nmcp. Nothing to install.
knowledge_base is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the knowledge_base 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.
Set action: deny in the PolicyLayer policy for knowledge_base. 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.
knowledge_base is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue