Evaluate external tools and command approvals before extending an agent.
Coding & development · Documented · Documentation checked 2026-10-04
Cursor editor agents and Cloud Agents; Grok Bot has a separate shared-computer boundary.
Installed client, subscription, organization settings, repository access, and cloud environment determine capabilities.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Evaluate external tools and command approvals before extending an agent.
Plugins and MCP add capabilities beyond local editing. Cursor’s security documentation distinguishes reads, workspace edits, terminal approvals, and MCP calls. Command allowlists and automatic classifiers are best-effort controls, not hard isolation guarantees.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Inspect the current agent settings and existing external tools.
- Review a trusted server’s operations and account scope before connecting it.
- Keep sensitive commands and MCP actions behind approval.
- Test a harmless read and review exactly which files or service objects become accessible.
Worked example
Connect a read-only tracker source for a sample bug. The agent can use the description to plan a local patch without posting comments or changing issue status. Keep any wider actions unavailable rather than relying only on a polite prompt.
Read [approved issue] and propose a local fix plan. Confirm the issue identity and relevant code. Do not edit the tracker or call unrelated tools. Show the purpose and side effects of any command you need before running it.
Inspect and verify the result
Inspect actual requests and granted scopes in the external service. Check approval settings and excluded-file behavior. A connected server should not expose unnecessary destructive operations.
Limits and troubleshooting
Workspace edits can occur immediately and live reload may execute changed code. .cursorignore and approvals serve different purposes. Untrusted repository content can influence an agent; inspect the workspace before enabling broad tool access.
Data, permissions, and actions
External tools can receive code or change service data. Command execution uses allowed host authority. Apply least-privilege service permissions and managed controls appropriate to the risk, rather than treating a prompt or classifier as a sandbox.
Related reading
Cloud Agents and development environments
Prepare a remote repository workspace and review changes before merging.
A local UI repair with deliberate recovery
Fix a sample UI problem while preserving unrelated work.
A cloud change with source and environment review
Run a scoped remote task and hand off tested branches or pull requests.
Plugins, connectors, and skills
Separate packaged capabilities, reusable instructions, and the connections that let AI reach other software.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Agent security and approvals · Cursor
Agent fundamentals and checkpoints · Cursor