get_standings
AI agents call get_standings to retrieve information from Soccer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves league standings data for display and analysis. No description is available, but the naming convention, server context, and sibling tool patterns all indicate a read-only query operation that retrieves existing data without modification, deletion, or external execution. The blast radius of misuse is minimal—an agent could only access publicly available sports statistics.
From the tool's definition Tool name is 'get_standings' with no description provided. Context indicates this server retrieves 'league standings, team fixtures, player statistics, and real-time match events.' The 'get_' prefix and sibling tools (get_league_info, get_league_fixtures,…
Attacks that exploit this kind of access
get_standings. It is categorised as a Read tool in the Soccer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Soccer MCP Server MCP server in PolicyLayer and add a rule for get_standings: 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 Soccer MCP Server. Nothing to install.
get_standings 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_standings 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_standings. 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_standings is provided by the Soccer MCP Server MCP server (obinopaul/soccer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →