AI agents call horse_history 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 or queries horse racing historical data—a read-only operation with no side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal since it only exposes historical data already in the system. This is consistent with the server's stated purpose of enabling 'analysis' of racing data through conversation.
From the tool's definition The tool name 'horse_history' and description '特定の馬の過去レース戦績を取得' (retrieve past race records for a specific horse) indicate a retrieval operation that queries historical racing data without modification, deletion, or execution of commands.
Documented attack patterns abuse exactly the kind of access horse_history 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 horse_history:
{
"version": "1",
"default": "deny",
"tools": {
"horse_history": {}
}
}horse_history 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 horse_history: 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.
horse_history 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 horse_history 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 horse_history. 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.
horse_history 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.