check_collabora

Check Collabora Online Office server health via GET /api/v1/config. 200 or 400 = server running. Default port 9980.

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-collabora.md

WHAT IT DOES

What check_collabora does on Mcp Nettools

AI agents call check_collabora 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_collabora is rated Low

The tool makes a simple health check query to a Collabora Online server using HTTP GET, which is a non-destructive read operation. It returns status information (200 or 400 response codes indicate server running state) without side effects. The blast radius of misuse is minimal—an attacker could discover if a Collabora server is running, but cannot modify data, execute commands, or cause harm.

From the tool's definition Tool performs a GET request to check server health status (/api/v1/config), which is a read-only operation that queries server state without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_collabora 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_collabora, this is the rule to start with:

check_collabora Allowed

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

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_collabora call is checked against it from then on.

FAQ

Questions about check_collabora

What does the check_collabora tool do? +

Check Collabora Online Office server health via GET /api/v1/config. 200 or 400 = server running. Default port 9980. 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_collabora? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_collabora: 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_collabora? +

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

Can I rate-limit check_collabora? +

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

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

check_collabora 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 →