get_check_telemetry

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-check-telemetry.md

WHAT IT DOES

What get_check_telemetry does on Freedom Mcp

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

Parameter	Type	Required	Description
`limit`	number	—	Max rows to return (default 50, hard cap 200).
`verdict`	string	—	Optional filter: pass \| fail \| flag \| hold \| error \| skipped.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`check_name`	string	—	Optional filter: brand \| legal \| ethics \| security \| pledge_stamp \| icp_quality \| craft.
`content_grain`	string	—	Optional filter by content grain (the safety/topic axis).

Parameters from the server's own tool schema.

RISK

Why get_check_telemetry is rated Low

This tool retrieves and queries historical telemetry data about quality checks with no side effects. It enables inspection of pass/fail/flag/hold verdicts across brand, legal, ethics, security, and craft gates. The action is purely informational—answering analytical questions about which checks fire findings or hold content. There is no creation, modification, deletion, or external code execution.

From the tool's definition Tool name 'get_check_telemetry' and description states 'Read recent quality-check telemetry' and 'Returns per-(run,check) verdicts'. The description explicitly clarifies this is for querying/retrieving check results and verdicts across various gates.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_check_telemetry safely

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

get_check_telemetry Allowed

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

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

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

FAQ

Questions about get_check_telemetry

What does the get_check_telemetry tool do? +

Read recent quality-check telemetry for the current company. Returns per-(run,check) verdicts (pass/fail/flag/hold/error/skipped) across the brand/legal/ethics/security gates, the Pledge stamp, the ICP consult, and the craft gate — so you can see which checks fire findings, which HOLD content (false-hold rate), and which run clean. Use it to answer 'which gate holds the most for this company' or 'has the security gate ever fired on these posts'. Free-text preview fields are tagged as data. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_check_telemetry accept? +

get_check_telemetry accepts 5 parameters: limit, verdict, companyId, check_name, content_grain. Required: companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_check_telemetry? +

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

What risk level is get_check_telemetry? +

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

Can I rate-limit get_check_telemetry? +

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

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

get_check_telemetry is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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