bdl_get_players

Search or list players for a given sport. Supports pagination and name search.

SERVERSports Hub SOURCEmcp-sports-hub

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/io-github-lacausecrypto-sports-hub/bdl-get-players.md

WHAT IT DOES

What bdl_get_players does on Sports Hub

AI agents call bdl_get_players to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why bdl_get_players is rated Low

This tool retrieves player information from a sports database without side effects. It supports querying and filtering (search, list, pagination) but does not create, modify, delete, or execute any actions. Typical misuse would be limited to data enumeration or information gathering, which poses minimal risk.

From the tool's definition Tool description explicitly states 'Search or list players' with pagination and name search support. These are purely retrieval operations with no data modification, deletion, or external execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bdl_get_players safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bdl_get_players, this is the rule to start with:

bdl_get_players Allowed

bdl_get_players is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bdl_get_players": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sports Hub, apply this rule, and every bdl_get_players call is checked against it from then on.

FAQ

Questions about bdl_get_players

What does the bdl_get_players tool do? +

Search or list players for a given sport. Supports pagination and name search. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bdl_get_players? +

Register the Sports Hub MCP server in PolicyLayer and add a rule for bdl_get_players: 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 Sports Hub. Nothing to install.

What risk level is bdl_get_players? +

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

Can I rate-limit bdl_get_players? +

Yes. Add a rate_limit block to the bdl_get_players 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 bdl_get_players completely? +

Set action: deny in the PolicyLayer policy for bdl_get_players. 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 bdl_get_players? +

bdl_get_players is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sports Hub, and thousands of servers like it.

This server

All 396 Sports Hub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →