AI agents invoke cortex_run to trigger actions in Novyx. 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.
cortex_run most likely executes operations or commands ('run' is a strong execution verb). While the empty description lowers confidence slightly, the server's explicit governance over actions and the presence of approval workflows and audit trails indicate this tool performs actual execution rather than mere querying. Given the audit and rollback capabilities, these are likely Execute-category operations.
From the tool's definition Tool name 'cortex_run' combined with server context of 'governed actions' and 'rollback' suggests execution capability.
Documented attack patterns abuse exactly the kind of access cortex_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for cortex_run:
{
"version": "1",
"default": "deny",
"tools": {
"cortex_run": {
"limits": [
{
"counter": "cortex_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cortex_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
cortex_run. It is categorised as a Execute tool in the Novyx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Novyx MCP server in PolicyLayer and add a rule for cortex_run: 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 Novyx. Nothing to install.
cortex_run 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_run 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_run. 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_run is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.