check_jaeger

Check Jaeger distributed tracing UI and query API via GET / (UI) and /api/services. Returns whether the UI is reachable and whether the query API is responding with valid JSON. port: 16686 (default UI/query). For Jaeger collector, use port_check on port 14268 (HTTP) or 6831 (UDP).

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

WHAT IT DOES

What check_jaeger does on Mcp Nettools

AI agents call check_jaeger 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_jaeger is rated Low

This tool only performs GET requests to query the status of a Jaeger distributed tracing service. It checks UI reachability and validates JSON responses from the query API, which are passive read operations with no side effects. There is no data modification, deletion, code execution, or financial impact.

From the tool's definition Tool description states it performs GET requests to check reachability and query response validity: 'via GET / (UI) and /api/services' and 'Returns whether the UI is reachable and whether the query API is responding with valid JSON'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_jaeger Allowed

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

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

FAQ

Questions about check_jaeger

What does the check_jaeger tool do? +

How do I enforce a policy on check_jaeger? +

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

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

Can I rate-limit check_jaeger? +

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

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

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