search_and_wait

THE RISK

High Risk

Why search_and_wait needs a policy

This tool executes a search query against the NGSIEM security event system and blocks until results are returned. It triggers an external operation (a search execution) rather than simply reading pre-existing data. Misuse could involve executing broad or resource-intensive queries against security infrastructure, but it does not modify or delete data, keeping severity at medium.

From the tool's definition "Execute a NGSIEM search and automatically wait for results (blocking)"

Documented attack patterns abuse exactly the kind of access search_and_wait gives an agent:

POLICY

How to control search_and_wait

PolicyLayer is an MCP gateway — it sits between your AI agents and NGSIEM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_and_wait:

policy.json

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

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

Create a free account and register NGSIEM MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More NGSIEM MCP Server tools

Execute stop_search Cancel a running NGSIEM search. Read build_query Build a NGSIEM query from a template with parameters. Read get_available_repositories Get the list of NGSIEM repositories configured in this environment. Read get_query_best_practices Get NGSIEM query writing best practices for optimal performance. Read get_query_reference Get NGSIEM query language reference. Read get_repo_fieldset MANDATORY FIRST STEP: Discover ALL available fields in a NGSIEM repository. Read get_search_status Check the status of a running NGSIEM search and retrieve results if complete. Read list_templates List available pre-built NGSIEM query templates for security operations.

All 10 NGSIEM MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in NGSIEM MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_and_wait

What does the search_and_wait tool do? +

Execute a NGSIEM search and automatically wait for results (blocking). It is categorised as a Execute tool in the NGSIEM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on search_and_wait? +

Register the NGSIEM MCP Server MCP server in PolicyLayer and add a rule for search_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 NGSIEM MCP Server. Nothing to install.

What risk level is search_and_wait? +

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

Can I rate-limit search_and_wait? +

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

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

search_and_wait is provided by the NGSIEM MCP Server MCP server (rodkinal/cs-ngsiem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NGSIEM MCP Server tool call.

Start from NGSIEM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →