mls_get_matches
Get MLS matches with optional filtering by season, dates, or teams
This record as markdown: /tools/io-balldontlie-mcp/mls-get-matches.md
What mls_get_matches does on Mcp
AI agents call mls_get_matches to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mls_get_matches is rated Low
This tool retrieves sports match data from the BALLDONTLIE API with optional filters. It performs no side effects, creates no data, executes no external code, and makes no financial transactions. It is purely a data retrieval (Read) operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'mls_get_matches' and description 'Get MLS matches with optional filtering by season, dates, or teams' indicates data retrieval with no modification capabilities.
Attacks that exploit this kind of access
The rule that runs mls_get_matches safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mls_get_matches, this is the rule to start with:
mls_get_matches 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 Mcp, apply this rule, and every mls_get_matches call is checked against it from then on.
Questions about mls_get_matches
Get MLS matches with optional filtering by season, dates, or teams. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for mls_get_matches: 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 Mcp. Nothing to install.
mls_get_matches 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 mls_get_matches 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 mls_get_matches. 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.
mls_get_matches is provided by the MCP server (https://mcp.balldontlie.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue