AI agents call get_jc_match_odds to retrieve information from Jc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches and presents betting odds comparison data (implied probabilities, payout rates, best odds options) for a given match. It is a read/query operation with no side effects.
From the tool's definition 获取详细的赔率对比分析，包括隐含概率、返奖率、最佳赔率选项 — the tool retrieves and analyses odds data for a specific match
Attacks that exploit this kind of access
针对特定比赛（两队队名）获取详细的赔率对比分析，包括隐含概率、返奖率、最佳赔率选项。适合做投注决策前深入分析。. It is categorised as a Read tool in the Jc MCP Server, which means it retrieves data without modifying state.
Register the Jc MCP server in PolicyLayer and add a rule for get_jc_match_odds: 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 Jc. Nothing to install.
get_jc_match_odds 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_jc_match_odds 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_jc_match_odds. 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_jc_match_odds is provided by the Jc MCP server (li3jia4hao5-hue/jc-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 →