New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_listing_details

Get full details for a specific marketplace listing by its numeric ID.

SERVER3dawn SOURCE3DawnRH/3dawn-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/3dawn-mcp/get-listing-details.md

What get_listing_details does on 3dawn

AI agents call get_listing_details 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 get_listing_details is rated Low

This tool retrieves marketplace listing information by ID. It performs a read-only query operation with no capability to modify, delete, or execute external actions. The severity is low because unauthorized access to listing details carries minimal risk—marketplace listings are typically intended to be publicly viewable or user-accessible information.

From the tool's definition Tool name 'get_listing_details' and description 'Get full details for a specific marketplace listing by its numeric ID' indicate a retrieval operation that queries marketplace data without modification or side effects.

Questions about get_listing_details

What does the get_listing_details tool do? +

Get full details for a specific marketplace listing by its numeric ID. It is categorised as a Read tool in the 3dawn MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_listing_details? +

Register the 3dawn MCP server in PolicyLayer and add a rule for get_listing_details: 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.

What risk level is get_listing_details? +

get_listing_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_listing_details? +

Yes. Add a rate_limit block to the get_listing_details 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 get_listing_details completely? +

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

get_listing_details 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 3dawn's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.