AI agents use knowledge_put_entity 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 (adding/updating entities) without permanently destroying information. The changes are reversible through subsequent writes. Without evidence of deletion, encryption, or financial impact, Write is the appropriate category.
From the tool's definition Tool description states 'Add or update an entity in the knowledge graph' - uses 'add' and 'update' which are write operations that reversibly modify data.
Attacks that exploit this kind of access
Add or update an entity in the knowledge graph. 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_put_entity: 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_put_entity 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_put_entity 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_put_entity. 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_put_entity 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 →