stop_search · TermPipe MCP: Risk & Policy

WHAT IT DOES

What stop_search does on TermPipe MCP

AI agents invoke stop_search to trigger actions in TermPipe MCP. 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 stop_search needs a policy

This tool triggers an external operation (stopping and cleaning up a search process) whose effects depend on which search is active. While not destructive in itself (the search can be restarted), it executes a command that terminates an ongoing operation. The term 'clean up' suggests resource management/process termination.

From the tool's definition Tool name 'stop_search' combined with server description stating 'direct terminal access to execute commands' and 'persistent REPL sessions'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_search Rate-limited

stop_search 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": {
    "stop_search": {
      "limits": [
        {
          "counter": "stop_search_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 TermPipe MCP, so you can run agents against it safely.

FAQ

Questions about stop_search

What does the stop_search tool do? +

Stop and clean up a search. It is categorised as a Execute tool in the TermPipe MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_search? +

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

What risk level is stop_search? +

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

Can I rate-limit stop_search? +

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

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

stop_search is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.