boolean_search

THE RISK

Low Risk

Why boolean_search needs a policy

This tool retrieves or queries data using Boolean operators to find matching code patterns. It has no side effects, does not modify data, does not execute code, and does not perform destructive operations. It is fundamentally a read operation constrained to information retrieval.

From the tool's definition Tool description states 'Perform Google-like Boolean search' - a search operation with no modification capability.

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

POLICY

How to control boolean_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 boolean_search:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "boolean_search": {}
  }
}

boolean_search is read-only, so it stays allowed — but 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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CodeSeeker-MCP tools

Execute interactive_search Launch interactive TUI search mode (note: this starts an interactive session) 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 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about boolean_search

What does the boolean_search tool do? +

Perform Google-like Boolean search with AND, OR, NOT operators. It is categorised as a Read tool in the CodeSeeker-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on boolean_search? +

Register the CodeSeeker- MCP server in PolicyLayer and add a rule for boolean_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 boolean_search? +

boolean_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit boolean_search? +

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

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

boolean_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 →