Low Risk

matrix_joined_rooms

List rooms the authenticated user is in, with a name hint for each.

How to control matrix_joined_rooms ↓

What matrix_joined_rooms does on Crow

AI agents call matrix_joined_rooms 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_joined_rooms needs a policy

This tool retrieves information about the authenticated user's Matrix room memberships. It performs a read-only query of existing data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an attacker could enumerate rooms the user participates in, but cannot manipulate data or trigger external actions. This is a standard Read category tool.

From the tool's definition Tool description states 'List rooms' which is a retrieval operation with no side effects. The verb 'List' and the output-only nature (name hints for rooms) indicate a query operation.

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

How to control matrix_joined_rooms

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_joined_rooms:

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

matrix_joined_rooms 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_joined_rooms

What does the matrix_joined_rooms tool do? +

List rooms the authenticated user is in, with a name hint for each. 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_joined_rooms? +

Register the Crow MCP server in PolicyLayer and add a rule for matrix_joined_rooms: 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_joined_rooms? +

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

Can I rate-limit matrix_joined_rooms? +

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

Set action: deny in the PolicyLayer policy for matrix_joined_rooms. 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_joined_rooms? +

matrix_joined_rooms 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.