Low Risk

matrix_room_messages

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

How to control matrix_room_messages ↓

What matrix_room_messages does on Crow

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

Low Risk

Why matrix_room_messages needs a policy

This tool queries existing data from a Matrix room without creating, modifying, deleting, or executing any operations. The paginated retrieval of message history is a standard read operation.

From the tool's definition Tool retrieves 'message history for a room' and 'returns the most recent N events' — these are query operations with no modification or side effects.

Documented attack patterns abuse exactly the kind of access matrix_room_messages gives an agent:

How to control matrix_room_messages

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for matrix_room_messages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "matrix_room_messages": {}
  }
}

matrix_room_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.