Medium Risk

add_dns_record

Add a DNS record to a domain you own. Costs $0.10 USDC per record. IMPORTANT: Always add DNS records one at a time (sequentially, not in parallel). After registering a new domain, wait at least 30 seconds before adding DNS records.

Accepts URL/endpoint input (host)

Part of the Bloomfilter MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@bloomfilter/mcp-server Write Risk 2/5

AI agents use add_dns_record to create or modify resources in Bloomfilter. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call add_dns_record repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Bloomfilter.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-eronmmer-bloomfilter.yaml
tools:
  add_dns_record:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Bloomfilter policy for all 10 tools.

Tool Name add_dns_record
Category Write
Risk Level Medium

View all 10 tools →

Agents calling write-class tools like add_dns_record have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the add_dns_record tool do? +

Add a DNS record to a domain you own. Costs $0.10 USDC per record. IMPORTANT: Always add DNS records one at a time (sequentially, not in parallel). After registering a new domain, wait at least 30 seconds before adding DNS records.. It is categorised as a Write tool in the Bloomfilter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_dns_record? +

Add a rule in your Intercept YAML policy under the tools section for add_dns_record. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bloomfilter MCP server.

What risk level is add_dns_record? +

add_dns_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_dns_record? +

Yes. Add a rate_limit block to the add_dns_record rule in your Intercept 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 add_dns_record completely? +

Set action: deny in the Intercept policy for add_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 add_dns_record? +

add_dns_record is provided by the Bloomfilter MCP server (@bloomfilter/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Bloomfilter

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.