predict_match
AI agents call predict_match to retrieve information from GoalGorithm MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool generates forecasts and predictions based on statistical models without modifying data, executing code, deleting records, or moving money. Despite the empty description for this specific tool, the server's documented purpose (predictions and statistical analysis of soccer leagues) and sibling tools (get_league_table, list_leagues—both Read operations) indicate this is a data retrieval/computation tool.
From the tool's definition Tool named 'predict_match' with context indicating 'Provides soccer match predictions and league statistics using xG data and Poisson distribution models' and 'forecast outcomes, analyze team performance'.
Attacks that exploit this kind of access
predict_match. It is categorised as a Read tool in the GoalGorithm MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoalGorithm MCP Server MCP server in PolicyLayer and add a rule for predict_match: 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 GoalGorithm MCP Server. Nothing to install.
predict_match 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 predict_match 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 predict_match. 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.
predict_match is provided by the GoalGorithm MCP Server MCP server (tohoanganhai/goalgorithm-mcp). 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 →