search_tools

[Deprecated: use

SERVERQverisai SOURCEqverisai/qveris-agent-toolkit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/qverisai-qveris-agent-toolkit/search-tools.md

WHAT IT DOES

What search_tools does on Qverisai

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

RISK

Why search_tools is rated Low

Search and discovery functions that retrieve metadata about available capabilities are Read operations with minimal risk. The deprecation status and incomplete description lower impact further. No side effects, data modification, code execution, destructive actions, or financial operations are evident from the available information.

From the tool's definition Tool is explicitly marked as '[Deprecated: use' with incomplete description, indicating it is a search/discovery function.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_tools safely

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

search_tools Allowed

search_tools 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": {
    "search_tools": {}
  }
}

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

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

FAQ

Questions about search_tools

What does the search_tools tool do? +

[Deprecated: use. It is categorised as a Read tool in the Qverisai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_tools? +

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

What risk level is search_tools? +

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

Can I rate-limit search_tools? +

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

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

search_tools is provided by the Qverisai MCP server (qverisai/qveris-agent-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Qverisai, and thousands of servers like it.

This server

All 9 Qverisai 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 →