college_search
Search US colleges and universities by name, state, control type, size, or accreditor. Returns matching institutions with location, control, predominant degree, and enrollment.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/college-search.md
What college_search does on Livedatalink
AI agents call college_search 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 |
|---|---|---|---|
name | string | — | Substring of the institution name. |
size | string | — | Carnegie size bucket. |
limit | number | — | Max results, 1-100. Default 25. |
state | string | — | Two-letter state code (e.g. TX). |
control | string | — | Institutional control. |
accreditor | string | — | Substring match against the school's institutional accreditor. |
Parameters from the server's own tool schema.
Why college_search is rated Low
Even though college_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs college_search 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_search, this is the rule to start with:
college_search 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_search call is checked against it from then on.
Questions about college_search
Search US colleges and universities by name, state, control type, size, or accreditor. Returns matching institutions with location, control, predominant degree, and enrollment. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
college_search accepts 6 parameters: name, size, limit, state, control, accreditor. 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_search: 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_search 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_search 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_search. 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_search 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