price_history

Get weekly price trend for one item at a rollup scope (national / state / district / chain / urbanisation / region / chain_group). Oldest-first time series, up to 52 weeks. Use for questions like

Server ManaMurah MCP Server manamurah/mcp-server
Category Read
Risk class Low
Parameters 00 required

What price_history does on ManaMurah MCP Server

AI agents call price_history to retrieve information from ManaMurah MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why price_history needs a policy

This tool performs data retrieval only—it queries and returns historical price information with no side effects, state changes, or irreversible operations. It fits the 'Read' category definition: retrieves or queries data with no side effects. No financial transactions, code execution, or data modification occurs.

From the tool's definition Tool retrieves historical price trend data in time-series format (oldest-first, up to 52 weeks). Description explicitly states 'Get weekly price trend' with no mutation, deletion, or execution capabilities.

Questions about price_history

What does the price_history tool do? +

Get weekly price trend for one item at a rollup scope (national / state / district / chain / urbanisation / region / chain_group). Oldest-first time series, up to 52 weeks. Use for questions like. It is categorised as a Read tool in the ManaMurah MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on price_history? +

Register the ManaMurah MCP Server MCP server in PolicyLayer and add a rule for price_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 ManaMurah MCP Server. Nothing to install.

What risk level is price_history? +

price_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit price_history? +

Yes. Add a rate_limit block to the price_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.

How do I block price_history completely? +

Set action: deny in the PolicyLayer policy for price_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.

What MCP server provides price_history? +

price_history is provided by the ManaMurah MCP Server MCP server (manamurah/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.