AI agents call get-records to retrieve information from Cfbd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical team record information from the College Football Data API. It performs a simple data lookup with no side effects, no code execution, no data modification, and no destructive operations. The low severity reflects that misuse would only expose publicly available sports statistics, posing minimal security risk.
From the tool's definition Tool name 'get-records' and description 'Get team records' indicate a retrieval operation that queries existing college football statistics data without modification or execution.
Documented attack patterns abuse exactly the kind of access get-records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cfbd, and nothing reaches the server without passing your rules. This is the rule we recommend for get-records:
{
"version": "1",
"default": "deny",
"tools": {
"get-records": {}
}
}get-records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get team records. It is categorised as a Read tool in the Cfbd MCP Server, which means it retrieves data without modifying state.
Register the Cfbd MCP server in PolicyLayer and add a rule for get-records: 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 Cfbd. Nothing to install.
get-records 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 get-records 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 get-records. 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.
get-records is provided by the Cfbd MCP server (lenwood/cfbd-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cfbd, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Cfbd tools catalogued and risk-classified — across an index of 43,000+ MCP servers.