cortex_update_feature · Cortex MCP: Risk & Policy

WHAT IT DOES

What cortex_update_feature does on Cortex MCP

AI agents use cortex_update_feature 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.

WHY IT NEEDS A POLICY

Why cortex_update_feature needs a policy

This tool modifies feature data (updates status) reversibly within the Cortex persistent memory system. It does not execute arbitrary code or delete data, placing it in the Write category. Severity is medium because misuse could corrupt the agent's feature tracking and decision-making state, but changes are typically reversible and scoped to feature metadata.

From the tool's definition Tool name 'cortex_update_feature' with description 'Update feature status' indicates modification of existing data in a persistent memory/brain system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cortex_update_feature Rate-limited

cortex_update_feature stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cortex_update_feature": {
      "limits": [
        {
          "counter": "cortex_update_feature_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cortex MCP, so you can run agents against it safely.

FAQ

Questions about cortex_update_feature

What does the cortex_update_feature tool do? +

Update feature status. 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.

How do I enforce a policy on cortex_update_feature? +

Register the Cortex MCP server in PolicyLayer and add a rule for cortex_update_feature: 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.

What risk level is cortex_update_feature? +

cortex_update_feature is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cortex_update_feature? +

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

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

cortex_update_feature 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.