search_chats

Search chats by participant name, handle, or chat name.

SERVERIconnect SOURCEiconnect-mcp

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/io-github-heznpc-iconnect/search-chats.md

WHAT IT DOES

What search_chats does on Iconnect

AI agents call search_chats to retrieve information from Iconnect 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_chats is rated Low

This tool queries existing chat data based on search criteria (participant name, handle, or chat name) and returns results. It does not create, modify, delete, or execute any operations — it is a pure read/retrieval function. The blast radius is low as the tool only returns information the user already has access to.

From the tool's definition Tool name is 'search_chats' and description states it 'Search chats by participant name, handle, or chat name' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_chats safely

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

search_chats Allowed

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

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

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

FAQ

Questions about search_chats

What does the search_chats tool do? +

Search chats by participant name, handle, or chat name. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_chats? +

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

What risk level is search_chats? +

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

Can I rate-limit search_chats? +

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

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

search_chats is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect 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 →