Search for messages across Matrix rooms. Search for specific content within messages. Can search all rooms or a specific room. Args: - query: Text to search for in messages - room_id: Optional room ID to limit search scope - limit: Maximum results (1-50, default 10) Returns: - Matching messages w...
AI agents call matrix_search_messages to retrieve information from Element MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing message data from Matrix rooms without creating, modifying, deleting, or executing any operations. It is purely a search/read function with limited blast radius if misused by an AI agent—worst case would be exposure of message content the user can already access.
From the tool's definition Tool description states 'Search for messages across Matrix rooms' and 'Search for specific content within messages.' Returns 'Matching messages with room, sender, and content' — a retrieval operation with no modification, deletion, or execution of…
Attacks that exploit this kind of access
Search for messages across Matrix rooms. Search for specific content within messages. Can search all rooms or a specific room. Args: - query: Text to search for in messages - room_id: Optional room ID to limit search scope - limit: Maximum results (1-50, default 10) Returns: - Matching messages with room, sender, and content. It is categorised as a Read tool in the Element MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Element MCP Server MCP server in PolicyLayer and add a rule for matrix_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 Element MCP Server. Nothing to install.
matrix_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 matrix_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 matrix_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.
matrix_search_messages is provided by the Element MCP Server MCP server (rosquillas/element-mcp-server). 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 →