beta-search

Beta search tool gated behind beta-search flag (enabled)

SERVERFrontmcp SOURCEagentfront/frontmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/beta-search.md

WHAT IT DOES

What beta-search does on Frontmcp

AI agents call beta-search to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why beta-search is rated Low

The term 'search' combined with the description characterizes this as a data retrieval tool. The 'beta' prefix and feature flag indicate it is experimental but does not change its fundamental purpose—querying or retrieving information. No evidence suggests it modifies, deletes, executes arbitrary code, or commits financial transactions.

From the tool's definition Tool name 'beta-search' and description 'Beta search tool gated behind beta-search flag' indicates a search functionality. Search tools retrieve or query data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs beta-search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For beta-search, this is the rule to start with:

beta-search Allowed

beta-search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "beta-search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every beta-search call is checked against it from then on.

FAQ

Questions about beta-search

What does the beta-search tool do? +

Beta search tool gated behind beta-search flag (enabled). It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on beta-search? +

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

What risk level is beta-search? +

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

Can I rate-limit beta-search? +

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

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

beta-search is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →