get_market_product
AI agents call get_market_product to retrieve information from Market Price Finder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve product information from marketplaces. No modification, deletion, code execution, or financial operations are implied. The low severity reflects minimal risk even if misused—retrieving product data poses no blast radius. Confidence is high despite empty description due to clear contextual alignment with the server's stated read-only query functionality.
From the tool's definition Tool name 'get_market_product' combined with server purpose of 'querying and comparing product prices across different marketplaces' and sibling tool 'search_market_product' indicates data retrieval.
Attacks that exploit this kind of access
get_market_product. It is categorised as a Read tool in the Market Price Finder MCP Server, which means it retrieves data without modifying state.
Register the Market Price Finder MCP server in PolicyLayer and add a rule for get_market_product: 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 Price Finder. Nothing to install.
get_market_product 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_product 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_product. 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_product is provided by the Market Price Finder MCP server (robuno/market-finder-ts-mcp-remote-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 →