Register a Matrix appservice (used by F.12 matrix-bridges bundle). Writes the registration YAML into Dendrite
AI agents use matrix_register_appservice 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.
This tool creates/registers a new appservice configuration by writing YAML into the Dendrite Matrix server. It's a Write operation (creates new configuration/registration), but carries high severity because registering a rogue appservice could grant broad access to Matrix rooms and messages, effectively acting as a privileged bridge with wide blast radius if misused.
From the tool's definition Register a Matrix appservice...Writes the registration YAML into Dendrite
Documented attack patterns abuse exactly the kind of access matrix_register_appservice gives an agent:
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_register_appservice:
{
"version": "1",
"default": "deny",
"tools": {
"matrix_register_appservice": {
"limits": [
{
"counter": "matrix_register_appservice_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}matrix_register_appservice 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.
Free to start. No card required.
Register a Matrix appservice (used by F.12 matrix-bridges bundle). Writes the registration YAML into Dendrite. 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_register_appservice: 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_register_appservice 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_register_appservice 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_register_appservice. 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_register_appservice 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.
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.