search_listings
Search the catalog of KYA-verified sellers. Public — no auth needed.
This record as markdown: /tools/com-get4agent-marketplace/search-listings.md
What search_listings does on Marketplace
AI agents call search_listings to retrieve information from Marketplace 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 |
|---|---|---|---|
kind | string | — | good | service | api | tool |
query | string | — | keyword (title/description) |
category | string | — | |
verified_only | boolean | — | default true |
Parameters from the server's own tool schema.
Why search_listings is rated Low
Even though search_listings only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_listings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Marketplace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_listings, this is the rule to start with:
search_listings 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 Marketplace, apply this rule, and every search_listings call is checked against it from then on.
Questions about search_listings
Search the catalog of KYA-verified sellers. Public — no auth needed. It is categorised as a Read tool in the Marketplace MCP Server, which means it retrieves data without modifying state.
search_listings accepts 4 parameters: kind, query, category, verified_only. The full parameter table on this page comes from the server's own tool schema.
Register the Marketplace MCP server in PolicyLayer and add a rule for search_listings: 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 Marketplace. Nothing to install.
search_listings 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_listings 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_listings. 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_listings is provided by the Marketplace MCP server (https://get4agent.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Marketplace, and thousands of servers like it.
This server
Across the catalogue