Full-text search Rocket.Chat messages. Searches across ALL cached
AI agents call search_messages to retrieve information from Rocket Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs full-text search across cached Rocket.Chat messages, which is a non-destructive read operation. It retrieves and queries data without side effects, reversibility requirements, or external execution. The sibling tools (get_messages, get_mentions, get_thread_messages, get_unread) reinforce that this server's read operations have low blast radius.
From the tool's definition Tool name 'search_messages' and description 'Full-text search Rocket.Chat messages' indicate a read-only query operation.
Attacks that exploit this kind of access
Full-text search Rocket.Chat messages. Searches across ALL cached. It is categorised as a Read tool in the Rocket Cli MCP Server, which means it retrieves data without modifying state.
Register the Rocket Cli MCP server in PolicyLayer and add a rule for search_messages: 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 Rocket Cli. Nothing to install.
search_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_messages 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.
Set action: deny in the PolicyLayer policy for search_messages. 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.
search_messages is provided by the Rocket Cli MCP server (jeanfbrito/rocket-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →