search
Search public App Store applications by term Search public App Store applications by term. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/search
This record as markdown: /tools/com-replynodes-mcp/search.md
What search does on ReplyNodes
AI agents call search to retrieve information from ReplyNodes 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 |
|---|---|---|---|
num | integer | — | Number of results; values outside 1..50 are rejected. |
lang | string | — | Language code. |
page | integer | — | Result page. |
term | string | Yes | Search term. |
country | string | — | Two-letter storefront code. |
idsOnly | boolean | — | Return ids without detail lookups. |
Parameters from the server's own tool schema.
Why search is rated Low
Queries public App Store data with no side effects or data modification capability.
From the tool's definition Search public App Store applications by term. Returns normalized public contract
Attacks that exploit this kind of access
The rule that runs search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search, this is the rule to start with:
search 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 ReplyNodes, apply this rule, and every search call is checked against it from then on.
Questions about search
Search public App Store applications by term Search public App Store applications by term. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/search. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
search accepts 6 parameters: num, lang, page, term, country, idsOnly. Required: term. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for search: 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 ReplyNodes. Nothing to install.
search 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 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. 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 is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue