matrix_room_messages

Paginated message history for a room. Returns the most recent N events by default.

SERVERCrow SOURCEkh0pper/crow

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/kh0pper-crow/matrix-room-messages.md

WHAT IT DOES

What matrix_room_messages does on Crow

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

RISK

Why matrix_room_messages is rated Low

This tool queries and retrieves historical messages from a Matrix room in a paginated manner. It has no side effects—it does not create, modify, delete, or execute anything. The blast radius of misuse is limited to unauthorized access to message content, which is a confidentiality concern but not integrity or availability risk.

From the tool's definition Tool description states it 'Returns the most recent N events' from room message history, indicating a retrieval operation with no modification, creation, or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs matrix_room_messages safely

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

matrix_room_messages Allowed

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

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

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

FAQ

Questions about matrix_room_messages

What does the matrix_room_messages tool do? +

Paginated message history for a room. Returns the most recent N events by default. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on matrix_room_messages? +

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

What risk level is matrix_room_messages? +

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

Can I rate-limit matrix_room_messages? +

Yes. Add a rate_limit block to the matrix_room_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.

How do I block matrix_room_messages completely? +

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

What MCP server provides matrix_room_messages? +

matrix_room_messages is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

The MCP Attack Database →

Guides

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