shop_app_analysis
Analyze Shop.app query results. Returns a market snapshot derived from Shop.app search results, including price ranges, currencies, sale counts, discounts, and top shops. Limit defaults to 20 and accepts values up to 50.
This record as markdown: /tools/crawlora-mcp/shop-app-analysis.md
What shop_app_analysis does on Crawlora
AI agents call shop_app_analysis to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum products to analyze, defaults to 20 and supports up to 50 |
query | string | Yes | Search query |
on_sale | boolean | — | Request sale products |
in_stock | boolean | — | Request in-stock products |
deep_search | boolean | — | Enable Shop.app deep search mode |
Parameters from the server's own tool schema.
Why shop_app_analysis is rated Low
This tool retrieves and aggregates existing market data from Shop.app without modifying, executing code, or causing side effects. It is a straightforward data retrieval and analysis function. The limit parameter (defaulting to 20, up to 50) controls result scope but does not indicate write or destructive capabilities.
From the tool's definition The tool 'Analyze Shop.app query results' returns aggregated market data (price ranges, currencies, sale counts, discounts, top shops) derived from search results. Keywords indicate read-only analysis: 'Analyze', 'Returns', 'snapshot', 'derived from'.
Attacks that exploit this kind of access
The rule that runs shop_app_analysis safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For shop_app_analysis, this is the rule to start with:
shop_app_analysis is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every shop_app_analysis call is checked against it from then on.
Questions about shop_app_analysis
Analyze Shop.app query results. Returns a market snapshot derived from Shop.app search results, including price ranges, currencies, sale counts, discounts, and top shops. Limit defaults to 20 and accepts values up to 50. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
shop_app_analysis accepts 5 parameters: limit, query, on_sale, in_stock, deep_search. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for shop_app_analysis: 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 Crawlora. Nothing to install.
shop_app_analysis 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 shop_app_analysis 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 shop_app_analysis. 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.
shop_app_analysis is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue