cursor_send_and_wait · Vscode MCP: Risk & Policy

WHAT IT DOES

What cursor_send_and_wait does on Vscode

AI agents invoke cursor_send_and_wait to trigger actions in Vscode. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why cursor_send_and_wait needs a policy

This tool sends messages to an AI agent and waits for its response, effectively triggering agentic execution within Cursor. The agent can perform arbitrary IDE operations (file edits, shell commands, etc.) based on the message sent.

From the tool's definition Send a message to the current Cursor agent chat and wait (blocking) until Cursor finishes responding

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cursor_send_and_wait Rate-limited

cursor_send_and_wait stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cursor_send_and_wait": {
      "limits": [
        {
          "counter": "cursor_send_and_wait_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vscode, so you can run agents against it safely.

FAQ

Questions about cursor_send_and_wait

What does the cursor_send_and_wait tool do? +

Send a message to the current Cursor agent chat and wait (blocking) until Cursor finishes responding. Returns the full response text. Use since_ms from cursor_open_chat to scope to the current session. It is categorised as a Execute tool in the Vscode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cursor_send_and_wait? +

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

What risk level is cursor_send_and_wait? +

cursor_send_and_wait is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cursor_send_and_wait? +

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

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

cursor_send_and_wait is provided by the Vscode MCP server (kloutdevs/vscode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.