pressable_delete_dns_record

Delete a specific DNS record.

Server Pressable MCP Server pcwprops/pressable-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What pressable_delete_dns_record does on Pressable MCP Server

AI agents call pressable_delete_dns_record to permanently remove resources in Pressable MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why pressable_delete_dns_record needs a policy

This tool permanently removes DNS records, which cannot be undone and would directly impact site accessibility and email routing. DNS record deletion is irreversible and qualifies as Destructive. Severity is high because misconfiguration could take a domain offline, though it is not financial in nature. The confidence is high given the explicit 'delete' verb and clear operational impact.

From the tool's definition Tool name 'pressable_delete_dns_record' and description 'Delete a specific DNS record' explicitly indicate irreversible deletion of DNS configuration data.

Questions about pressable_delete_dns_record

What does the pressable_delete_dns_record tool do? +

Delete a specific DNS record. It is categorised as a Destructive tool in the Pressable MCP Server 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 pressable_delete_dns_record? +

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

What risk level is pressable_delete_dns_record? +

pressable_delete_dns_record 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 pressable_delete_dns_record? +

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

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

pressable_delete_dns_record is provided by the Pressable MCP Server MCP server (pcwprops/pressable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

pressable_delete_dns_record is one line of Pressable MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.