Force pause, queue a question for human, block until answered via POST /api/human-answer
AI agents invoke cortex_ask_human to trigger actions in Cortex MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (blocking the agent loop and queuing an interaction via an HTTP endpoint) whose effects depend on runtime arguments. It halts execution flow and interacts with an external API, making it Execute category. Severity is high because misuse could deadlock or stall an AI agent indefinitely, or manipulate human-in-the-loop approval flows.
From the tool's definition Force pause, queue a question for human, block until answered via POST /api/human-answer
Attacks that exploit this kind of access
Force pause, queue a question for human, block until answered via POST /api/human-answer. It is categorised as a Execute tool in the Cortex MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_ask_human: 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 Cortex MCP. Nothing to install.
cortex_ask_human is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cortex_ask_human 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 cortex_ask_human. 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.
cortex_ask_human is provided by the Cortex MCP server (neuralnexustech/cortex-mcp). 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 →