Initialize Cortex project. You MUST ask the human ALL 10 onboarding questions FIRST using cortex_ask_human.
AI agents use cortex_init to create or update resources in Cortex MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cortex MCP environment.
This tool creates new project state in Cortex's persistent storage system. While not destructive (reversible) or immediately dangerous compared to Execute or Financial tools, it modifies the knowledge base/memory that subsequent tool calls may depend upon.
From the tool's definition Tool name 'cortex_init' and description 'Initialize Cortex project' indicate creation/setup of a new project structure. This is a write operation that creates persistent state in a 'memory' system (per server description), though it is reversible.
Attacks that exploit this kind of access
Initialize Cortex project. You MUST ask the human ALL 10 onboarding questions FIRST using cortex_ask_human. It is categorised as a Write tool in the Cortex MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_init: 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_init is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cortex_init 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_init. 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_init 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 →