AI agents use assistant_axis_session_end 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 terminates an active monitoring session and retrieves final metrics. Ending a session is a state-modifying action (Write) that closes/finalizes a session record. It is not destructive in the sense of permanently deleting data, and it retrieves a summary as a side effect. The blast radius is medium since terminating a session prematurely or unintentionally could disrupt ongoing monitoring workflows.
From the tool's definition End a monitoring session and get final metrics summary
Attacks that exploit this kind of access
End a monitoring session and get final metrics summary. 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 assistant_axis_session_end: 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_session_end 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 assistant_axis_session_end 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_session_end. 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_session_end 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 →