AI agents call jockey_stats to retrieve information from JVLink 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 and analyzes historical jockey performance data from the JRA-VAN database. It has no side effects, does not modify data, execute arbitrary code, delete records, or involve financial transactions. The blast radius of misuse is minimal—worst case would be exposure of publicly available horse racing statistics.
From the tool's definition Tool name 'jockey_stats' and description '騎手の成績を分析' (analyze jockey performance) indicates data retrieval and analysis of racing statistics.
Documented attack patterns abuse exactly the kind of access jockey_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JVLink MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for jockey_stats:
{
"version": "1",
"default": "deny",
"tools": {
"jockey_stats": {}
}
}jockey_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
騎手の成績を分析. It is categorised as a Read tool in the JVLink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JVLink MCP Server MCP server in PolicyLayer and add a rule for jockey_stats: 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 JVLink MCP Server. Nothing to install.
jockey_stats 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 jockey_stats 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 jockey_stats. 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.
jockey_stats is provided by the JVLink MCP Server MCP server (miyamamoto/jvlink-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JVLink MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 JVLink MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.