Create relation between knowledge items
AI agents use relate_knowledge to create or update resources in MemoDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MemoDB MCP Server environment.
This tool creates new associations or connections between knowledge items, which is a write operation that modifies the knowledge base structure. It is reversible (relations can be deleted) and has a medium blast radius - misuse could create unwanted associations or pollute the knowledge graph, but cannot irreversibly destroy data or execute arbitrary code.
From the tool's definition Tool name 'relate_knowledge' and description 'Create relation between knowledge items' indicate creation of new relationships/links between existing data.
Attacks that exploit this kind of access
Create relation between knowledge items. It is categorised as a Write tool in the MemoDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MemoDB MCP Server MCP server in PolicyLayer and add a rule for relate_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 MemoDB MCP Server. Nothing to install.
relate_knowledge 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 relate_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.
Set action: deny in the PolicyLayer policy for relate_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.
relate_knowledge is provided by the MemoDB MCP Server MCP server (wuyunmei/momedb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →