remove_local_a_record

THE RISK

Critical Risk

Why remove_local_a_record needs a policy

This tool deletes DNS configuration data (A records) from Pi-hole's local DNS settings. DNS record deletion is irreversible and affects network resolution for potentially many clients relying on those records. While the confirmation token provides some protection against accidental use, the core function is destructive.

From the tool's definition Tool name contains 'remove' and description states 'Remove a local A record from Pi-hole'. Removal of DNS records is an irreversible deletion operation that cannot be undone without manual re-entry.

Documented attack patterns abuse exactly the kind of access remove_local_a_record gives an agent:

POLICY

How to control remove_local_a_record

PolicyLayer is an MCP gateway — it sits between your AI agents and Pi-hole MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_local_a_record:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_local_a_record"
  ]
}

remove_local_a_record disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Pi-hole MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pi-hole MCP Server tools

Destructive remove_local_cname_record Remove a local CNAME record from Pi-hole with confirmation token Write add_local_a_record Add a local A record to Pi-hole Write add_local_cname_record Add a local CNAME record to Pi-hole Read list_local_dns List local A and CNAME records from Pi-hole Read list_queries Fetch recent DNS query history with filtering options Read list_query_history Get activity graph data for Pi-hole queries over time Read list_query_suggestions Get query filter suggestions for Pi-hole query data

All 8 Pi-hole MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Pi-hole MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_local_a_record

What does the remove_local_a_record tool do? +

Remove a local A record from Pi-hole with confirmation token. It is categorised as a Destructive tool in the Pi-hole 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 remove_local_a_record? +

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

What risk level is remove_local_a_record? +

remove_local_a_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 remove_local_a_record? +

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

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

remove_local_a_record is provided by the Pi-hole MCP Server MCP server (sbarbett/pihole-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pi-hole MCP Server tool call.

Start from Pi-hole MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →