AI agents use knowledge_add_relation to create or update resources in Musubix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Musubix environment.
This tool creates or modifies data by establishing relationships between entities, which is reversible (relations can typically be removed). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'knowledge_add_relation' and description 'Add a relation between two entities' indicate creation/modification of data. The 'add' verb denotes a Write operation that creates new relational links in a knowledge graph or database.
Attacks that exploit this kind of access
Add a relation between two entities. It is categorised as a Write tool in the Musubix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Musubix MCP server in PolicyLayer and add a rule for knowledge_add_relation: 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 Musubix. Nothing to install.
knowledge_add_relation 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_add_relation 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_add_relation. 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_add_relation is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). 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 →