workflows-get_status
AI agents call workflows-get_status to retrieve information from MCP Search Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_status' naming pattern strongly indicates a query operation that retrieves workflow state without modification. Status checks are typically non-destructive reads. The empty description prevents verification but naming conventions and the read-oriented server context support this classification. Misuse risk is minimal: an agent invoking this cannot modify data or trigger external actions.
From the tool's definition Tool name 'workflows-get_status' indicates status retrieval with no mutation suffix (get, not set/delete/create). Server context is a search/workflow engine providing information retrieval.
Attacks that exploit this kind of access
workflows-get_status. It is categorised as a Read tool in the MCP Search Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Search Server MCP server in PolicyLayer and add a rule for workflows-get_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 MCP Search Server. Nothing to install.
workflows-get_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 workflows-get_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 workflows-get_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.
workflows-get_status is provided by the MCP Search Server MCP server (nghiauet/mcp-agent). 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 →