This record as markdown: /tools/io-github-lacausecrypto-sports-hub/msf-get-roster.md
What msf_get_roster does on Sports Hub
AI agents call msf_get_roster 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.
Why msf_get_roster is rated Low
This tool retrieves publicly available sports roster data. There are no modifications, deletions, executions, or financial implications. The blast radius of misuse is minimal—returning incorrect or excessive roster data causes no harm to systems or data integrity. Low severity reflects the read-only, informational nature of the operation.
From the tool's definition Tool name 'msf_get_roster' and description 'Get the roster for a specific team' indicate a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs msf_get_roster 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 msf_get_roster, this is the rule to start with:
msf_get_roster 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 Sports Hub, apply this rule, and every msf_get_roster call is checked against it from then on.
Questions about msf_get_roster
Get the roster for a specific team. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for msf_get_roster: 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.
msf_get_roster 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 msf_get_roster 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 msf_get_roster. 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.
msf_get_roster 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.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue