AI agents call cortex_config to retrieve information from Novyx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data without modifying, deleting, or executing anything. It poses minimal risk as configuration reads typically expose non-sensitive metadata or settings that an AI agent would need to understand system state. The governance context (audit, rollback, approval workflows) further suggests this is a safe introspection capability.
From the tool's definition Tool name 'cortex_config' with description 'Get the current Cortex configuration' indicates a retrieval operation. The verb 'Get' and lack of any modification language clearly signal a read-only action.
Documented attack patterns abuse exactly the kind of access cortex_config 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_config:
{
"version": "1",
"default": "deny",
"tools": {
"cortex_config": {}
}
}cortex_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current Cortex configuration. It is categorised as a Read tool in the Novyx MCP Server, which means it retrieves data without modifying state.
Register the Novyx MCP server in PolicyLayer and add a rule for cortex_config: 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_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cortex_config 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_config. 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_config 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.