browse_drops
Browse NFT drops on 3Dawn — time-limited slot sales with bonding curve pricing.
This record as markdown: /tools/3dawn-mcp/browse-drops.md
What browse_drops does on 3dawn
AI agents call browse_drops to retrieve information from 3dawn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why browse_drops is rated Low
This tool retrieves and displays information about NFT drops (marketplace listings with bonding curve pricing). It performs no creation, modification, deletion, code execution, or financial transaction. Browsing is a passive data retrieval operation analogous to search or list operations. Blast radius is minimal—an AI agent cannot cause unintended harm by querying drop information.
From the tool's definition Tool name 'browse_drops' and description 'Browse NFT drops' indicate data retrieval. The verb 'browse' and context of querying time-limited sales data with pricing information matches read-only query behavior with no side effects.
Attacks that exploit this kind of access
The rule that runs browse_drops safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3dawn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_drops, this is the rule to start with:
browse_drops 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 3dawn, apply this rule, and every browse_drops call is checked against it from then on.
Questions about browse_drops
Browse NFT drops on 3Dawn — time-limited slot sales with bonding curve pricing. It is categorised as a Read tool in the 3dawn MCP Server, which means it retrieves data without modifying state.
Register the 3dawn MCP server in PolicyLayer and add a rule for browse_drops: 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 3dawn. Nothing to install.
browse_drops 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 browse_drops 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 browse_drops. 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.
browse_drops is provided by the 3dawn MCP server (3DawnRH/3dawn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3dawn, and thousands of servers like it.
This server
Across the catalogue