crow_pm_bot_telemetry

Dispatch-rail telemetry: totals by disposition, accept rate (accepted / decided — edits and rejections both count against it), boundary violation count, and a per-bot breakdown of the same numbers.

SERVERCrow SOURCEkh0pper/crow

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/kh0pper-crow/crow-pm-bot-telemetry.md

WHAT IT DOES

What crow_pm_bot_telemetry does on Crow

AI agents call crow_pm_bot_telemetry to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why crow_pm_bot_telemetry is rated Low

Tool retrieves and reports telemetry metrics without modifying, executing, or deleting any data.

From the tool's definition telemetry totals, accept rate, per-bot breakdown; no modification of data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_pm_bot_telemetry safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_pm_bot_telemetry, this is the rule to start with:

crow_pm_bot_telemetry Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about crow_pm_bot_telemetry

What does the crow_pm_bot_telemetry tool do? +

Dispatch-rail telemetry: totals by disposition, accept rate (accepted / decided — edits and rejections both count against it), boundary violation count, and a per-bot breakdown of the same numbers. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_pm_bot_telemetry? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_pm_bot_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 Crow. Nothing to install.

What risk level is crow_pm_bot_telemetry? +

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

Can I rate-limit crow_pm_bot_telemetry? +

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

Set action: deny in the PolicyLayer policy for crow_pm_bot_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 crow_pm_bot_telemetry? +

crow_pm_bot_telemetry is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 602 Crow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →