college_metrics
Cost and outcome metrics for one school: published tuition (in-state and out-of-state), average net price, six-year graduation rate, first-year retention, median earnings ten years after entry, admission rate, and SAT/ACT ranges.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/college-metrics.md
What college_metrics does on Livedatalink
AI agents call college_metrics to retrieve information from Livedatalink 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 |
|---|---|---|---|
unit_id | string | Yes | IPEDS UNITID (Scorecard 'id'). |
Parameters from the server's own tool schema.
Why college_metrics is rated Low
This tool queries and returns pre-computed institutional data with no side effects. It is purely informational retrieval about publicly available college statistics. There is no capacity to modify records, execute code, delete data, or commit financial transactions. The low severity reflects minimal risk from misuse—returning factual educational metrics poses no security or operational threat.
From the tool's definition Tool retrieves published educational metrics for a college: tuition, graduation rate, retention, earnings, admission rate, and standardized test ranges.
Attacks that exploit this kind of access
The rule that runs college_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For college_metrics, this is the rule to start with:
college_metrics 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 Livedatalink, apply this rule, and every college_metrics call is checked against it from then on.
Questions about college_metrics
Cost and outcome metrics for one school: published tuition (in-state and out-of-state), average net price, six-year graduation rate, first-year retention, median earnings ten years after entry, admission rate, and SAT/ACT ranges. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
college_metrics accepts 1 parameter: unit_id. Required: unit_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for college_metrics: 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 Livedatalink. Nothing to install.
college_metrics 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 college_metrics 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 college_metrics. 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.
college_metrics is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue