cortex_tick_file · Cortex MCP: Risk & Policy

WHAT IT DOES

What cortex_tick_file does on Cortex MCP

AI agents use cortex_tick_file 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_tick_file needs a policy

This tool writes metadata or checkpoint state about files rather than creating, deleting, or executing arbitrary operations. It modifies the internal state of the memory/tracking system (marking completion status and saving checkpoints), which is a write operation.

From the tool's definition Tool marks files as "created/done" and "saves checkpoint if file exists on disk." These are reversible state modifications—the checkpoint can be overwritten or the marking removed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cortex_tick_file Rate-limited

cortex_tick_file 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_tick_file": {
      "limits": [
        {
          "counter": "cortex_tick_file_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_tick_file

What does the cortex_tick_file tool do? +

Mark a file as created/done in file tree. Saves checkpoint if file exists on disk. 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_tick_file? +

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

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

Can I rate-limit cortex_tick_file? +

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

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

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