check_tempo

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

WHAT IT DOES

What check_tempo does on Mcp Nettools

AI agents call check_tempo 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_tempo is rated Low

The tool retrieves status information from a Grafana Tempo service via GET requests. This is a query/diagnostic operation with no side effects, no code execution, no data modification, and no destructive capabilities. The low severity reflects the minimal blast radius—an agent could only gather information about service availability, not affect system state or data.

From the tool's definition Tool description states it performs GET requests to /ready and /api/echo endpoints to check readiness status and API responsiveness. These are read-only health check operations with no data modification, deletion, or execution of arbitrary commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_tempo Allowed

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

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

FAQ

Questions about check_tempo

What does the check_tempo tool do? +

Check Grafana Tempo distributed tracing service via GET /ready and /api/echo. Returns readiness status and whether the API is responding. port: 3200 (default HTTP), 9095 (gRPC — use port_check for gRPC). 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_tempo? +

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

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

Can I rate-limit check_tempo? +

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

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

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