cortex_tool_stats

View Cortex MCP tool usage analytics: success rates, latency, token estimates, and trends. Use to measure Cortex effectiveness and identify flaky tools. Available to all team members.

ServerCortex Hub
CategoryRead

How to control cortex_tool_stats ↓

WHAT IT DOES

What cortex_tool_stats does on Cortex Hub

AI agents call cortex_tool_stats to retrieve information from Cortex Hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why cortex_tool_stats needs a policy

This tool retrieves and displays usage statistics and performance metrics—purely observational data collection with no side effects. It does not create, modify, delete, execute code, or move resources. The blast radius of misuse is minimal; an agent could only gather information about tool performance, which presents no operational risk.

From the tool's definition Tool description states 'View Cortex MCP tool usage analytics: success rates, latency, token estimates, and trends.' The verbs 'view' and 'measure' indicate read-only retrieval of historical analytics data with no modification, deletion, or execution of…

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

POLICY

How to control cortex_tool_stats

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_tool_stats:

policy.json

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

cortex_tool_stats 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_tool_stats

What does the cortex_tool_stats tool do? +

View Cortex MCP tool usage analytics: success rates, latency, token estimates, and trends. Use to measure Cortex effectiveness and identify flaky tools. Available to all team members. 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_tool_stats? +

Register the Cortex Hub MCP server in PolicyLayer and add a rule for cortex_tool_stats: 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_tool_stats? +

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

Can I rate-limit cortex_tool_stats? +

Yes. Add a rate_limit block to the cortex_tool_stats 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_tool_stats completely? +

Set action: deny in the PolicyLayer policy for cortex_tool_stats. 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_tool_stats? +

cortex_tool_stats 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 →

Free to start. No card required.

25 Cortex Hub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.