start_search · TermPipe MCP: Risk & Policy

WHAT IT DOES

What start_search does on TermPipe MCP

AI agents invoke start_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 start_search needs a policy

With no explicit description, classification must rely on context: the server explicitly offers terminal command execution, and 'start_search' sits alongside file operations (append_file, analyze_file_structure) and system tools (boot, build, daemon_send). Search operations typically invoke executables (find, grep, etc.) that run external processes.

From the tool's definition Tool is part of TermPipe MCP which 'Provides AI assistants with direct terminal access to execute commands' and 'manage files'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_search Rate-limited

start_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": {
    "start_search": {
      "limits": [
        {
          "counter": "start_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 start_search

What does the start_search tool do? +

start_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 start_search? +

Register the TermPipe MCP server in PolicyLayer and add a rule for start_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 start_search? +

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

Can I rate-limit start_search? +

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

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

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