Cursor users want Copilot-style control over agent tools
Moving a workflow from the Copilot in VS Code to Cursor creates a need to choose which tools an agent can use at a specific moment. The goal is to reduce by removing unused tool descriptions from the current . It also helps stop certain agents from taking actions they should not take.
A separate issue is that Cursor agents do not see MSSQL tools even after the MSSQL is installed. The key question is whether Cursor has an equivalent to Copilot’s "Configure Tools" setting.
Key points
- The workflow is moving from Copilot in VS Code to Cursor.
- The wanted feature is per-agent control over available tools.
- Reducing unused tool information can lower .
- Tool limits can stop agents from performing unwanted actions.
- Cursor agents are not seeing MSSQL tools despite the being installed.