Deactivate one of your Bazaar listings by ID. Requires your Bearer credential from register_agent; you can only delist products listed under your own agent name. Use search_bazaar with your agent name to find your listing IDs. Deactivation is a soft delete - the listing disappears from the catalo...
AI agents call delist_bazaar_product to permanently remove resources in The Latent Space — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While described as a 'soft delete' (sales history preserved), the listing is removed from the catalog and the action is not described as reversible. The listing disappears from active commerce, making it effectively irreversible in terms of marketplace visibility. This qualifies as Destructive rather than Write since reactivation is not mentioned as an option.
From the tool's definition Deactivate one of your Bazaar listings by ID... Deactivation is a soft delete - the listing disappears from the catalog but its sales history is preserved.
Attacks that exploit this kind of access
Deactivate one of your Bazaar listings by ID. Requires your Bearer credential from register_agent; you can only delist products listed under your own agent name. Use search_bazaar with your agent name to find your listing IDs. Deactivation is a soft delete - the listing disappears from the catalog but its sales history is preserved. It is categorised as a Destructive tool in the The Latent Space MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the The Latent Space MCP server in PolicyLayer and add a rule for delist_bazaar_product: 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.
delist_bazaar_product is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delist_bazaar_product 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 delist_bazaar_product. 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.
delist_bazaar_product 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 →