check_matrix_synapse

Check Matrix Synapse homeserver health via GET /_matrix/federation/v1/version (public endpoint). Returns server version.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-matrix-synapse.md

WHAT IT DOES

What check_matrix_synapse does on Mcp Nettools

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

RISK

Why check_matrix_synapse is rated Low

This tool only retrieves information from a public API endpoint without side effects. It queries the health status and version of a Matrix Synapse homeserver. Even if misused by an AI agent, the only risk is information disclosure about the target server's software version, which is already publicly accessible. This is a classic Read operation with minimal blast radius.

From the tool's definition The tool performs a GET request to a public endpoint (/_matrix/federation/v1/version) to retrieve server version information. The description explicitly states it 'Returns server version' with no modification, deletion, or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_matrix_synapse safely

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

check_matrix_synapse Allowed

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

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

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

FAQ

Questions about check_matrix_synapse

What does the check_matrix_synapse tool do? +

Check Matrix Synapse homeserver health via GET /_matrix/federation/v1/version (public endpoint). Returns server version. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_matrix_synapse? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_matrix_synapse: 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 Mcp Nettools. Nothing to install.

What risk level is check_matrix_synapse? +

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

Can I rate-limit check_matrix_synapse? +

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

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

check_matrix_synapse is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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