send_message_without_waiting · MCP IDE Bridge MCP

WHAT IT DOES

What send_message_without_waiting does on MCP IDE Bridge

AI agents use send_message_without_waiting to create or update resources in MCP IDE Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP IDE Bridge environment.

WHY IT NEEDS A POLICY

Why send_message_without_waiting needs a policy

This tool creates or modifies data (messages) in a reversible manner by sending communication between clients. It falls under Write rather than Execute because it transmits data rather than triggering computational side effects. The 'without_waiting' variant suggests asynchronous fire-and-forget semantics, which could allow an agent to send many messages rapidly.

From the tool's definition Tool name 'send_message_without_waiting' indicates it sends messages asynchronously. The server description confirms it enables 'bidirectional messaging' between IDEs and AI agents. No description provided for the tool itself, limiting specificity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_message_without_waiting Rate-limited

send_message_without_waiting 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_message_without_waiting": {
      "limits": [
        {
          "counter": "send_message_without_waiting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about send_message_without_waiting

What does the send_message_without_waiting tool do? +

send_message_without_waiting. It is categorised as a Write tool in the MCP IDE Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_message_without_waiting? +

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

What risk level is send_message_without_waiting? +

send_message_without_waiting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_message_without_waiting? +

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

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

send_message_without_waiting is provided by the MCP IDE Bridge MCP server (wiltshirek/mcp-ide-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.