check_authelia

Check Authelia authentication server health via GET /api/health. Returns healthy when service is up. Default port 9091.

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

WHAT IT DOES

What check_authelia does on Mcp Nettools

AI agents call check_authelia 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_authelia is rated Low

This tool retrieves health status information from an Authelia authentication server via a read-only GET request. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an attacker could only learn whether a service is running. This is a straightforward diagnostic query tool.

From the tool's definition Tool performs a GET request to /api/health endpoint to check service status. Returns health information only, no modification or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_authelia Allowed

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

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

FAQ

Questions about check_authelia

What does the check_authelia tool do? +

Check Authelia authentication server health via GET /api/health. Returns healthy when service is up. Default port 9091. 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_authelia? +

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

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

Can I rate-limit check_authelia? +

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

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

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