AI agents call workflow_status to retrieve information from QueryNest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
workflow_status retrieves and displays metadata about an ongoing workflow state. It has no side effects, cannot modify data, execute commands, or trigger external operations. This is a read-only informational tool with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description indicates it 'views current query workflow status, progress and next step suggestions' — purely observational with no data modification, deletion, or code execution.
Attacks that exploit this kind of access
查看当前查询工作流的状态、进度和下一步建议. It is categorised as a Read tool in the QueryNest MCP Server, which means it retrieves data without modifying state.
Register the QueryNest 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 QueryNest. 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 QueryNest MCP server (niuzaishu/querynest). 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 →