AI agents use team_add_knowledge 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 new entries in a knowledge base, which is a write operation. It doesn't delete, execute code, move money, or trigger external operations—it simply adds informational content. Severity is medium because misuse could introduce incorrect or misleading information into a shared knowledge base, but the effect is reversible (entries can be edited or removed).
From the tool's definition Tool description states it 'adds new entries' (新しいエントリを追加します) to a team knowledge base, including decisions, lessons learned, best practices, and warnings. This is a create/modify operation that adds data reversibly.
Attacks that exploit this kind of access
チームのナレッジベースに新しいエントリを追加します。決定、教訓、ベストプラクティス、警告などを共有できます。. 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 team_add_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 Musubix. Nothing to install.
team_add_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 team_add_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 team_add_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.
team_add_knowledge 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 →