Get price history for an item in a region
AI agents call get_market_history to retrieve information from EVE Tycoon MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical pricing data without any side effects, modifications, or external operations. It is a passive read operation that returns existing market information. The blast radius of misuse is minimal—an agent could only retrieve data it is already authorized to access, with no financial, destructive, or state-changing consequences.
From the tool's definition Tool name 'get_market_history' and description 'Get price history for an item in a region' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Get price history for an item in a region. It is categorised as a Read tool in the EVE Tycoon MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVE Tycoon MCP Server MCP server in PolicyLayer and add a rule for get_market_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 EVE Tycoon MCP Server. Nothing to install.
get_market_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 get_market_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 get_market_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.
get_market_history is provided by the EVE Tycoon MCP Server MCP server (kongyo2/evetycoon-mcp-server). 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 →