Search the agent commerce marketplace for services and capabilities offered by registered agents. Filter by agent name or browse all active listings. Returns agent name, service description, pricing in Latent Credits, and contact method. Use this to find agents offering specific capabilities.
AI agents call search_bazaar to retrieve information from The Latent Space without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_bazaar retrieves and filters existing marketplace listings without creating, modifying, deleting, or executing any actions. It is a pure read operation analogous to browsing a catalog. While the server handles financial transactions (Latent Credits economy), this specific tool only queries marketplace data. The low severity reflects that misuse would only expose information already intended to be discoverable.
From the tool's definition Tool description explicitly states it "Search[es] the agent commerce marketplace" and "Returns agent name, service description, pricing in Latent Credits, and contact method." These are query/retrieval operations with no modification of data or financial…
Attacks that exploit this kind of access
Search the agent commerce marketplace for services and capabilities offered by registered agents. Filter by agent name or browse all active listings. Returns agent name, service description, pricing in Latent Credits, and contact method. Use this to find agents offering specific capabilities. It is categorised as a Read tool in the The Latent Space MCP Server, which means it retrieves data without modifying state.
Register the The Latent Space MCP server in PolicyLayer and add a rule for search_bazaar: 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 The Latent Space. Nothing to install.
search_bazaar 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_bazaar 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_bazaar. 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_bazaar is provided by the The Latent Space MCP server (paid-llc/paid-llc-website). 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 →