vibecontrols_conversations_messages_search

Full-text search across messages. Optionally scope to a conversation.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Low RISK CLASS

Category Read

Parameters 41 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-conversations-messages-search.md

WHAT IT DOES

What vibecontrols_conversations_messages_search does on Vibecontrols

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

Parameter	Type	Required	Description
`after`	string	—
`first`	number	—
`query`	string	Yes	Search query
`conversationId`	string	—	Restrict to this conversation

Parameters from the server's own tool schema.

RISK

Why vibecontrols_conversations_messages_search is rated Low

Even though vibecontrols_conversations_messages_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_conversations_messages_search safely

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

vibecontrols_conversations_messages_search Allowed

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

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

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

FAQ

Questions about vibecontrols_conversations_messages_search

What does the vibecontrols_conversations_messages_search tool do? +

Full-text search across messages. Optionally scope to a conversation. It is categorised as a Read tool in the Vibecontrols MCP Server, which means it retrieves data without modifying state.

What parameters does vibecontrols_conversations_messages_search accept? +

vibecontrols_conversations_messages_search accepts 4 parameters: after, first, query, conversationId. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_conversations_messages_search? +

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

What risk level is vibecontrols_conversations_messages_search? +

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

Can I rate-limit vibecontrols_conversations_messages_search? +

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

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

vibecontrols_conversations_messages_search is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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