Search the Malaysian PriceCatcher item catalogue by name in any language (Malay/English/Chinese/Tamil). Use this FIRST when the user mentions a food item by name to resolve it to the item_code that every other tool requires. Returns up to 20 matches with translations. Do not use for prices — chai...
AI agents call search_items 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.
This tool performs a straightforward catalogue search operation that retrieves item metadata (codes, names, translations, categories) from a read-only government price database. It has no ability to modify data, execute code, delete records, or trigger financial transactions.
From the tool's definition Tool description explicitly states it 'Search[es] the Malaysian PriceCatcher item catalogue by name' and 'Returns up to 20 matches with translations.' The description emphasizes 'Do not use for prices — chain to find_cheapest or price_history next,'…
Attacks that exploit this kind of access
Search the Malaysian PriceCatcher item catalogue by name in any language (Malay/English/Chinese/Tamil). Use this FIRST when the user mentions a food item by name to resolve it to the item_code that every other tool requires. Returns up to 20 matches with translations. Do not use for prices — chain to find_cheapest or price_history next. Tip: the full active item list (code + Malay/English name + category) is also available as the. It is categorised as a Read tool in the ManaMurah MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ManaMurah MCP Server MCP server in PolicyLayer and add a rule for search_items: 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.
search_items 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 search_items 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 search_items. 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.
search_items 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.
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 →