check_loki

Check Grafana Loki log aggregation service via GET /ready and /loki/api/v1/status/buildinfo. Returns readiness status and build 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-loki.md

WHAT IT DOES

What check_loki does on Mcp Nettools

AI agents call check_loki 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_loki is rated Low

This tool queries the status and health of a Grafana Loki service without modifying any data or triggering any operations. It retrieves diagnostic information only, with no side effects or ability to affect system state. This is a typical health-check/monitoring operation classified as Read with low severity due to minimal impact if misused.

From the tool's definition Tool performs GET requests to health/status endpoints (/ready and /loki/api/v1/status/buildinfo) to retrieve readiness status and build version information. Uses HTTP GET method which is a read-only operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_loki Allowed

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

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

FAQ

Questions about check_loki

What does the check_loki tool do? +

Check Grafana Loki log aggregation service via GET /ready and /loki/api/v1/status/buildinfo. Returns readiness status and build 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_loki? +

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

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

Can I rate-limit check_loki? +

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

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

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