catalog_search
FREE. Keyword-search every PulseNetwork endpoint (name, description, action, params). Returns matching endpoints with vertical, action, price, params, and base URL — the fastest way to find the right paid endpoint for a task. No wallet or payment needed.
This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/catalog-search.md
What catalog_search does on Pulsenetwork
AI agents call catalog_search to retrieve information from Pulsenetwork 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 |
|---|---|---|---|
max | string | — | Max results (default 10, cap 25) |
query | string | Yes | Keywords to search for, e.g. "flight delay compensation" or "token honeypot scan" |
Parameters from the server's own tool schema.
Why catalog_search is rated Low
Retrieves metadata about available endpoints without executing queries or transactions.
From the tool's definition Keyword-search, returns matching endpoints, no payment needed.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs catalog_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For catalog_search, this is the rule to start with:
catalog_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 Pulsenetwork, apply this rule, and every catalog_search call is checked against it from then on.
Questions about catalog_search
FREE. Keyword-search every PulseNetwork endpoint (name, description, action, params). Returns matching endpoints with vertical, action, price, params, and base URL — the fastest way to find the right paid endpoint for a task. No wallet or payment needed. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
catalog_search accepts 2 parameters: max, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for catalog_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 Pulsenetwork. Nothing to install.
catalog_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 catalog_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 catalog_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.
catalog_search is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pulsenetwork, and thousands of servers like it.
This server
Across the catalogue