AI agents call workflow_status 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 only queries and retrieves workflow state information without creating, modifying, deleting, or executing any operations. It is a pure read operation that has no side effects on the workflow or system state. The low severity reflects minimal blast radius if misused by an AI agent—it can only expose existing workflow information.
From the tool's definition Tool name 'workflow_status' and description indicate it 'retrieves the current state of a workflow' (ワークフローの現在の状態を取得します), including phase status, progress rate, and artifact information. The verb 'get/取得' confirms data retrieval with no modification.
Attacks that exploit this kind of access
ワークフローの現在の状態を取得します。 各フェーズの状態、進捗率、アーティファクト情報を含みます。. 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 workflow_status: 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.
workflow_status 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 workflow_status 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 workflow_status. 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.
workflow_status 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 →