brain_build
Add knowledge, reasoning patterns, behavior rules, or skills to a brain. Layers: knowledge — concepts, facts, rules, glossary terms reasoning — decomposition patterns, decision frameworks, question triggers behavior — personality traits, communication style, boundaries skills — capability modules...
This record as markdown: /tools/io-github-0nork-0nmcp/brain-build.md
What brain_build does on 0nmcp
AI agents use brain_build 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 brain_build is rated Medium
This tool creates or modifies data within a brain construct by adding layers (knowledge, reasoning, behavior, skills, scenarios). It is a Write operation as it persistently modifies an AI brain's configuration.
From the tool's definition Add knowledge, reasoning patterns, behavior rules, or skills to a brain
Attacks that exploit this kind of access
The rule that runs brain_build 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 brain_build, this is the rule to start with:
brain_build 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 brain_build call is checked against it from then on.
Questions about brain_build
Add knowledge, reasoning patterns, behavior rules, or skills to a brain. Layers: knowledge — concepts, facts, rules, glossary terms reasoning — decomposition patterns, decision frameworks, question triggers behavior — personality traits, communication style, boundaries skills — capability modules, tool mappings scenarios — test scenarios with expected behavior Example: brain_build({ brain_id:. 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 brain_build: 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.
brain_build 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 brain_build 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 brain_build. 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.
brain_build 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