特定日の価格データを取得
AI agents call get_price_on_date to retrieve information from Market Index MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical market index price information for a specified date. It performs a pure query operation against historical data with no capability to modify, delete, or execute operations. The worst-case misuse would be information gathering, which poses minimal risk. Consistent with sibling tools (get_daily_prices, get_price_range, etc.) which are all Read operations.
From the tool's definition Tool name 'get_price_on_date' and description indicating retrieval of price data ('特定日の価格データを取得' = 'Get price data for a specific date') matches the Read category pattern of querying/fetching historical data without side effects.
Attacks that exploit this kind of access
特定日の価格データを取得. It is categorised as a Read tool in the Market Index MCP MCP Server, which means it retrieves data without modifying state.
Register the Market Index MCP server in PolicyLayer and add a rule for get_price_on_date: 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 Market Index MCP. Nothing to install.
get_price_on_date 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_price_on_date 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_price_on_date. 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_price_on_date is provided by the Market Index MCP server (tamappe/market-index-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 →