get_dogfood_telemetry
Query dogfood telemetry rows with optional filters. Returns matching rows plus computed averages (tool calls, latency, cost, judge score).
This record as markdown: /tools/io-github-homenshum-nodebench/get-dogfood-telemetry.md
What get_dogfood_telemetry does on Nodebench
AI agents call get_dogfood_telemetry to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dogfood_telemetry is rated Low
This tool retrieves and queries telemetry data with optional filters, returning aggregated information. It performs no destructive operations, does not modify state, does not execute code or commands, and does not involve financial transactions. The output is computed metrics (averages of tool calls, latency, cost, judge score) from existing telemetry rows.
From the tool's definition 'Query dogfood telemetry rows' and 'Returns matching rows plus computed averages' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_dogfood_telemetry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dogfood_telemetry, this is the rule to start with:
get_dogfood_telemetry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every get_dogfood_telemetry call is checked against it from then on.
Questions about get_dogfood_telemetry
Query dogfood telemetry rows with optional filters. Returns matching rows plus computed averages (tool calls, latency, cost, judge score). It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for get_dogfood_telemetry: 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 Nodebench. Nothing to install.
get_dogfood_telemetry is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_dogfood_telemetry 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.
Set action: deny in the PolicyLayer policy for get_dogfood_telemetry. 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.
get_dogfood_telemetry is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue