record_dogfood_telemetry

Record a full telemetry row for a dogfood run. Captures surface, scenario, user role, prompt, tool usage, token estimates, latency, cost, and quality scores.

SERVERNodebench SOURCEnodebench-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/record-dogfood-telemetry.md

WHAT IT DOES

What record_dogfood_telemetry does on Nodebench

AI agents use record_dogfood_telemetry to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.

RISK

Why record_dogfood_telemetry is rated Medium

This tool writes/creates a new telemetry record (a 'row') in some data store. It captures and stores observational data about a run. While it involves 'cost' fields, it does not move money or commit financial obligations—it merely records cost metadata. The action is reversible (a record can be deleted), so it falls under Write rather than Destructive or Financial.

From the tool's definition Record a full telemetry row for a dogfood run. Captures surface, scenario, user role, prompt, tool usage, token estimates, latency, cost, and quality scores.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

record_dogfood_telemetry Rate-limited

record_dogfood_telemetry stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_dogfood_telemetry": {
      "limits": [
        {
          "counter": "record_dogfood_telemetry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every record_dogfood_telemetry call is checked against it from then on.

FAQ

Questions about record_dogfood_telemetry

What does the record_dogfood_telemetry tool do? +

Record a full telemetry row for a dogfood run. Captures surface, scenario, user role, prompt, tool usage, token estimates, latency, cost, and quality scores. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_dogfood_telemetry? +

Register the Nodebench MCP server in PolicyLayer and add a rule for record_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.

What risk level is record_dogfood_telemetry? +

record_dogfood_telemetry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_dogfood_telemetry? +

Yes. Add a rate_limit block to the record_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.

How do I block record_dogfood_telemetry completely? +

Set action: deny in the PolicyLayer policy for record_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.

What MCP server provides record_dogfood_telemetry? +

record_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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →