cortex_task_status

THE RISK

Low Risk

Why cortex_task_status needs a policy

This tool queries and retrieves information about a task's state, logs, and historical records without side effects. It is a read-only inspection operation typical of status/monitoring endpoints. No creation, modification, deletion, or code execution is described or implied.

From the tool's definition Tool performs a 'Get' operation to retrieve task status, logs, and history with no modification or execution capability indicated. The verb 'Get' and description 'Get the detailed status' clearly indicate data retrieval only.

Documented attack patterns abuse exactly the kind of access cortex_task_status gives an agent:

POLICY

How to control cortex_task_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex Hub, and nothing reaches the server without passing your rules. This is the rule we recommend for cortex_task_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cortex_task_status": {}
  }
}

cortex_task_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Cortex Hub — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cortex Hub tools

Execute cortex_code_reindex Trigger re-indexing of a project after code changes. Looks up the project by repo URL and Execute cortex_cypher Run Cypher queries directly against the GitNexus knowledge graph. Supports MATCH, RETURN, Write cortex_session_start Start a new execution session with optional agent identity metadata. Write cortex_knowledge_store Store a knowledge document in the Cortex knowledge base. Auto-chunks and embeds the conten Write cortex_memory_store Store a memory for an AI agent. Memories persist across sessions and can be recalled by se Write cortex_session_end Close a session with a summary of work done. Reports session duration and compliance. Write cortex_task_accept Accept an assigned task, signaling that work will begin. Updates task status to accepted. Write cortex_task_create Create a task and optionally assign it to another agent. Use for delegating work, tracking

All 25 Cortex Hub tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cortex_task_status

What does the cortex_task_status tool do? +

Get the detailed status of a specific task including its logs and history. It is categorised as a Read tool in the Cortex Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cortex_task_status? +

Register the Cortex Hub MCP server in PolicyLayer and add a rule for cortex_task_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 Cortex Hub. Nothing to install.

What risk level is cortex_task_status? +

cortex_task_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cortex_task_status? +

Yes. Add a rate_limit block to the cortex_task_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.

How do I block cortex_task_status completely? +

Set action: deny in the PolicyLayer policy for cortex_task_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.

What MCP server provides cortex_task_status? +

cortex_task_status is provided by the Cortex Hub MCP server (lktiep/cortex-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cortex Hub tool call.

Start from Cortex Hub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →