Critical Risk →

nexbid_purchase

<tool_description> Initiate a purchase for a product found via nexbid_search. Returns a checkout link that the user can click to complete the purchase at the retailer. The agent should present this link to the user for confirmation. </tool_description> <when_to_use> ONLY after user has expressed ...

Risk signalsHigh parameter count (11 properties)

Part of the Discovery server.

nexbid_purchase can permanently delete data in Discovery, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DISCOVERY →

Free to start. No card required.

AI agents may call nexbid_purchase to permanently remove or destroy resources in Discovery. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call nexbid_purchase in a loop, permanently destroying resources in Discovery. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "nexbid_purchase"
  ]
}

See the full Discovery policy for all 19 tools.

Get this rule live on your own Discovery server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DISCOVERY →

View all 19 tools →

These attack patterns abuse exactly the kind of access nexbid_purchase gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so nexbid_purchase only ever does what you allow.

SECURE DISCOVERY →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the nexbid_purchase tool do? +

<tool_description> Initiate a purchase for a product found via nexbid_search. Returns a checkout link that the user can click to complete the purchase at the retailer. The agent should present this link to the user for confirmation. </tool_description> <when_to_use> ONLY after user has expressed clear purchase intent for a specific product. Requires a product UUID from nexbid_search or nexbid_product. ALWAYS confirm with user before calling this tool. </when_to_use> <combination_hints> nexbid_search (purchase intent) → nexbid_purchase → present checkout link to user. After purchase → nexbid_order_status to check if completed. Use checkout_mode=wallet_pay when the user has a connected wallet with active mandate. </combination_hints> <output_format> For prefill_link (default): Checkout URL that the user clicks to complete purchase at the retailer. For wallet_pay: Intent ID and status for mandate-based authorization. Include product name and price for user confirmation. </output_format>. It is categorised as a Destructive tool in the Discovery MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on nexbid_purchase? +

Register the Discovery MCP server in PolicyLayer and add a rule for nexbid_purchase: 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 Discovery. Nothing to install.

What risk level is nexbid_purchase? +

nexbid_purchase is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit nexbid_purchase? +

Yes. Add a rate_limit block to the nexbid_purchase 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.

How do I block nexbid_purchase completely? +

Set action: deny in the PolicyLayer policy for nexbid_purchase. 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.

What MCP server provides nexbid_purchase? +

nexbid_purchase is provided by the Discovery MCP server (https://mcp.nexbid.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Discovery tool call.

Deterministic rules across all 19 Discovery tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.