AI agents call assistant_axis_phase_check to retrieve information from Musubix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and reports monitoring parameters for a workflow phase. It performs no mutations, does not execute external operations, and has no irreversible effects. The read-only nature and low blast radius (retrieving monitoring metadata) place it firmly in the Read category with low severity.
From the tool's definition Tool name contains 'check' and description states 'Check monitoring level and frequency' — a query operation that retrieves configuration status without modification or side effects.
Attacks that exploit this kind of access
Check monitoring level and frequency for a specific workflow phase. It is categorised as a Read tool in the Musubix MCP Server, which means it retrieves data without modifying state.
Register the Musubix MCP server in PolicyLayer and add a rule for assistant_axis_phase_check: 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.
assistant_axis_phase_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the assistant_axis_phase_check 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 assistant_axis_phase_check. 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.
assistant_axis_phase_check 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 →