get-drives

THE RISK

Low Risk

Why get-drives needs a policy

This tool retrieves and analyzes drive statistics from college football games—a pure read operation with no side effects. It fits squarely within the 'Read' category alongside sibling tools (get-games, get-rankings, get-records, etc.), which all fetch data from the College Football Data API.

From the tool's definition Tool name is 'get-drives' and description states 'Analyze drive information', indicating retrieval and analysis of existing data. No modification, deletion, execution, or financial operations are indicated.

Documented attack patterns abuse exactly the kind of access get-drives gives an agent:

POLICY

How to control get-drives

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-drives:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-drives": {}
  }
}

get-drives is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Cfbd — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cfbd tools

Read get-advanced-box-score Access detailed game statistics and analytics Read get-games Retrieve game data Read get-games-teams Access team game statistics Read get-play-stats View play statistics Read get-plays Query play-by-play data Read get-pregame-win-probability See win probabilities Read get-rankings Check team rankings Read get-records Get team records

All 9 Cfbd tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-drives

What does the get-drives tool do? +

Analyze drive information. It is categorised as a Read tool in the Cfbd MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-drives? +

Register the Cfbd MCP server in PolicyLayer and add a rule for get-drives: 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.

What risk level is get-drives? +

get-drives is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-drives? +

Yes. Add a rate_limit block to the get-drives 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.

How do I block get-drives completely? +

Set action: deny in the PolicyLayer policy for get-drives. 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.

What MCP server provides get-drives? +

get-drives 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.

Enforce policy on every Cfbd tool call.

Start from Cfbd, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →