interactive_search

THE RISK

High Risk

Why interactive_search needs a policy

This tool launches an interactive terminal UI session, which constitutes executing an external process/application. Starting an interactive session can have broad side effects depending on what the user does within it, and an AI agent could potentially misuse it to run arbitrary commands or trigger further operations.

From the tool's definition 'Launch interactive TUI search mode' and 'this starts an interactive session'

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

POLICY

How to control interactive_search

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

policy.json

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

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

Create a free account and register CodeSeeker-MCP — 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 CodeSeeker-MCP tools

Write code_refactor Refactor code structures like function names, class names, etc. Write search_and_replace Search for patterns and replace them with new text (supports dry-run mode) Write bulk_replace Perform multiple search and replace operations in a single command Read basic_search Perform a basic text search using ugrep with optional filters and formatting Read boolean_search Perform Google-like Boolean search with AND, OR, NOT operators Read check_ugrep_installation Check if ugrep is installed and get installation instructions Read code_structure_search Search for specific code structures like functions, classes and methods Read fuzzy_search Perform fuzzy search that finds approximate matches allowing character errors

All 12 CodeSeeker-MCP 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 CodeSeeker-MCP → 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 interactive_search

What does the interactive_search tool do? +

Launch interactive TUI search mode (note: this starts an interactive session). It is categorised as a Execute tool in the CodeSeeker-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 interactive_search? +

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

What risk level is interactive_search? +

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

Can I rate-limit interactive_search? +

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

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

interactive_search is provided by the CodeSeeker- MCP server (mixelpixx/codeseeker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CodeSeeker-MCP tool call.

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

CHECK YOUR STACK →