Clear current QuantConnect authentication configuration. Returns: Dictionary containing operation status
AI agents call clear_quantconnect_auth to permanently remove resources in QuantConnect MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing authentication configuration is an irreversible action that removes stored credentials/config, effectively disconnecting the platform from QuantConnect. This cannot be undone without re-authenticating, and misuse by an AI agent could disrupt all trading platform operations. Classified as Destructive due to the permanent removal of configuration data.
From the tool's definition Clear current QuantConnect authentication configuration
Documented attack patterns abuse exactly the kind of access clear_quantconnect_auth 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 clear_quantconnect_auth:
{
"version": "1",
"default": "deny",
"hide": [
"clear_quantconnect_auth"
]
} clear_quantconnect_auth disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear current QuantConnect authentication configuration. Returns: Dictionary containing operation status. It is categorised as a Destructive tool in the QuantConnect MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for clear_quantconnect_auth: 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.
clear_quantconnect_auth is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_quantconnect_auth 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 clear_quantconnect_auth. 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.
clear_quantconnect_auth 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.