Update a project's name and/or description. Args: project_id: ID of the project to update name: Optional new name for the project description: Optional new description for the project Returns: Dictionary containing update result
AI agents use update_project 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.
This tool modifies project metadata (name and description) in a reversible manner. It does not execute code, delete data, move funds, or trigger external trading operations. The context of a trading platform makes this medium severity—an AI could misuse it to obfuscate or sabotage projects by renaming/redescribing them, but the changes can be undone.
From the tool's definition Tool description states it can 'Update a project's name and/or description' with optional parameters for modifying project metadata. The 'update' operation and reversible nature of renaming/describing a project indicate write capability.
Documented attack patterns abuse exactly the kind of access update_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuantConnect MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_project:
{
"version": "1",
"default": "deny",
"tools": {
"update_project": {
"limits": [
{
"counter": "update_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_project 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.
Free to start. No card required.
Update a project's name and/or description. Args: project_id: ID of the project to update name: Optional new name for the project description: Optional new description for the project Returns: Dictionary containing update result. 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.
Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for update_project: 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.
update_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_project 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 update_project. 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.
update_project is provided by the QuantConnect MCP Server MCP server (taylorwilsdon/quantconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 QuantConnect MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 QuantConnect MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.