This record as markdown: /tools/kh0pper-crow/matrix-invite-user.md
What matrix_invite_user does on Crow
AI agents use matrix_invite_user to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why matrix_invite_user is rated Medium
Inviting a user to a room is a reversible write action — it creates a membership invitation record. It can be undone by revoking or cancelling the invite. No data is deleted, no code is executed, and no financial transaction occurs. Medium severity because misuse could expose room contents to unintended users, but the blast radius is limited.
From the tool's definition Invite a user to a room
Attacks that exploit this kind of access
The rule that runs matrix_invite_user 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_invite_user, this is the rule to start with:
matrix_invite_user stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every matrix_invite_user call is checked against it from then on.
Questions about matrix_invite_user
Invite a user to a room. Rate-limited: 10/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for matrix_invite_user: 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.
matrix_invite_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the matrix_invite_user 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_invite_user. 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_invite_user 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue