Trigger: When the user asks to create a project-specific or domain-specific
AI agents use create_knowledge_base to create or update resources in MemOS — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MemOS environment.
This tool creates a new knowledge base, which is a reversible Write operation. It establishes a new data store but does not execute code, delete data irreversibly, or move money.
From the tool's definition Tool name is 'create_knowledge_base' and description indicates it creates a project-specific or domain-specific knowledge base. The verb 'create' is characteristic of Write operations that establish new data structures.
Documented attack patterns abuse exactly the kind of access create_knowledge_base gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MemOS, and nothing reaches the server without passing your rules. This is the rule we recommend for create_knowledge_base:
{
"version": "1",
"default": "deny",
"tools": {
"create_knowledge_base": {
"limits": [
{
"counter": "create_knowledge_base_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_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.
Free to start. No card required.
Trigger: When the user asks to create a project-specific or domain-specific. It is categorised as a Write tool in the MemOS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MemOS MCP server in PolicyLayer and add a rule for create_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 MemOS. Nothing to install.
create_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 create_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 create_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.
create_knowledge_base is provided by the MemOS MCP server (memtensor/memos-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MemOS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MemOS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.