dynadot_get_auction_bids

Get the bid history for an auction. NOTE: requires auction-API access.

SERVERDynadot SOURCEeyalm321/dynadot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-get-auction-bids.md

WHAT IT DOES

What dynadot_get_auction_bids does on Dynadot

AI agents call dynadot_get_auction_bids to retrieve information from Dynadot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why dynadot_get_auction_bids is rated Low

The tool only fetches and returns bid history records for an auction. It performs a read/query operation with no data modification, execution, or financial commitment. Severity is low since it only exposes auction bid data.

From the tool's definition 'Get the bid history for an auction' — retrieves historical bid data with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dynadot_get_auction_bids safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dynadot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dynadot_get_auction_bids, this is the rule to start with:

dynadot_get_auction_bids Allowed

dynadot_get_auction_bids is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynadot_get_auction_bids": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dynadot, apply this rule, and every dynadot_get_auction_bids call is checked against it from then on.

FAQ

Questions about dynadot_get_auction_bids

What does the dynadot_get_auction_bids tool do? +

Get the bid history for an auction. NOTE: requires auction-API access. It is categorised as a Read tool in the Dynadot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dynadot_get_auction_bids? +

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

What risk level is dynadot_get_auction_bids? +

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

Can I rate-limit dynadot_get_auction_bids? +

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

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

dynadot_get_auction_bids is provided by the Dynadot MCP server (eyalm321/dynadot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dynadot, and thousands of servers like it.

This server

All 105 Dynadot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →