dynadot_get_domain_push_request

List pending domain push requests for a domain.

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-domain-push-request.md

What dynadot_get_domain_push_request does on Dynadot

AI agents call dynadot_get_domain_push_request 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.

Why dynadot_get_domain_push_request is rated Low

This tool retrieves existing data (pending push requests) without modifying, deleting, executing external operations, or creating financial obligations. The operation is informational and reversible by nature. Severity is low because the data returned pertains to domain transfer requests, which while sensitive, does not directly compromise domain control or financial assets without further action.

From the tool's definition Tool name contains 'get' and description states 'List pending domain push requests' — both indicate a read-only query operation with no side effects.

Questions about dynadot_get_domain_push_request

What does the dynadot_get_domain_push_request tool do? +

List pending domain push requests for a domain. 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_domain_push_request? +

Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_get_domain_push_request: 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_domain_push_request? +

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

Can I rate-limit dynadot_get_domain_push_request? +

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

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

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

More on Dynadot, 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 Dynadot'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.