AI agents use team_share_pattern 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 writes/pushes code patterns to a Git branch for sharing with team members. It creates or modifies data in a Git repository (a reversible write operation). It does not appear to execute arbitrary code or destructively delete data, though pushing to a shared branch could have team-wide impact, warranting medium severity.
From the tool's definition チームとコードパターンを共有します。Gitブランチ経由で共有され、チームメンバーが採用できます。 (Shares code patterns with the team via Git branch, which team members can adopt)
Attacks that exploit this kind of access
チームとコードパターンを共有します。Gitブランチ経由で共有され、チームメンバーが採用できます。. 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_share_pattern: 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_share_pattern 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_share_pattern 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_share_pattern. 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_share_pattern 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 →