college_accreditation
Current institutional accreditation status, accreditor, and (when published by DAPIP) last action date and programmatic accreditations.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/college-accreditation.md
What college_accreditation does on Livedatalink
AI agents call college_accreditation 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. |
Parameters from the server's own tool schema.
Why college_accreditation is rated Low
This tool queries and returns static institutional accreditation information from a data source. It performs a read-only lookup with no side effects, no code execution, no data modification, and no financial impact. The blast radius of misuse is minimal—an agent could only retrieve publicly available accreditation data.
From the tool's definition Tool retrieves 'current institutional accreditation status, accreditor, and last action date and programmatic accreditations' — pure data retrieval with no modification, deletion, or external execution.
Attacks that exploit this kind of access
The rule that runs college_accreditation 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_accreditation, this is the rule to start with:
college_accreditation 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_accreditation call is checked against it from then on.
Questions about college_accreditation
Current institutional accreditation status, accreditor, and (when published by DAPIP) last action date and programmatic accreditations. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
college_accreditation 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_accreditation: 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_accreditation 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_accreditation 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_accreditation. 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_accreditation 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