college_trends
Multi-year trend for one school sourced from the Urban Institute Education Data Portal (IPEDS). Choose a metric (enrollment, graduation_rate, retention, cost) and a year range.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/college-trends.md
What college_trends does on Livedatalink
AI agents call college_trends 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 |
|---|---|---|---|
metric | string | Yes | Trend metric. |
unit_id | string | Yes | IPEDS UNITID. |
end_year | number | Yes | Last academic year, e.g. 2022. |
start_year | number | Yes | First academic year, e.g. 2010. |
Parameters from the server's own tool schema.
Why college_trends is rated Low
The tool queries and retrieves historical educational trend data from a public data portal. It supports filtering by metric and time period but does not create, modify, delete, or execute any operations. There are no side effects beyond returning requested information. This is a straightforward Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'Multi-year trend for one school sourced from the Urban Institute Education Data Portal (IPEDS)' with operations to 'Choose a metric...and a year range.' These are read-only data retrieval operations with no modification, deletion, or…
Attacks that exploit this kind of access
The rule that runs college_trends 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_trends, this is the rule to start with:
college_trends 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_trends call is checked against it from then on.
Questions about college_trends
Multi-year trend for one school sourced from the Urban Institute Education Data Portal (IPEDS). Choose a metric (enrollment, graduation_rate, retention, cost) and a year range. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
college_trends accepts 4 parameters: metric, unit_id, end_year, start_year. Required: metric, unit_id, end_year, start_year. 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_trends: 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_trends 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_trends 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_trends. 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_trends 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