update_file_name · QuantConnect MCP Server MCP

WHAT IT DOES

What update_file_name does on QuantConnect MCP Server

AI agents use update_file_name to create or update resources in QuantConnect MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuantConnect MCP Server environment.

WHY IT NEEDS A POLICY

Why update_file_name needs a policy

This tool modifies file metadata (renaming) in a non-destructive, reversible manner. It fits the Write category: creates or modifies data reversibly. The severity is low because renaming a file has minimal blast radius—the operation is easily undone, does not delete data, execute code, or affect financial transactions.

From the tool's definition Tool description states 'Update the name of a file' — a reversible modification operation that changes file metadata without altering content or executing code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_file_name Rate-limited

update_file_name 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": {
    "update_file_name": {
      "limits": [
        {
          "counter": "update_file_name_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 QuantConnect MCP Server, so you can run agents against it safely.

FAQ

Questions about update_file_name

What does the update_file_name tool do? +

Update the name of a file. It is categorised as a Write tool in the QuantConnect MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_file_name? +

Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for update_file_name: 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 QuantConnect MCP Server. Nothing to install.

What risk level is update_file_name? +

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

Can I rate-limit update_file_name? +

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

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

update_file_name is provided by the QuantConnect MCP Server MCP server (mymanish9-code11/quantconnect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.