create_dns_check · Pingera MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_dns_check does on Pingera MCP Server

AI agents use create_dns_check to create or update resources in Pingera MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pingera MCP Server environment.

WHY IT NEEDS A POLICY

Why create_dns_check needs a policy

Based on the tool name and context of sibling tools (create_check, create_icmp_check, create_heartbeat, etc.), this tool likely creates a DNS monitoring check in the Pingera service, which is a reversible write operation. Confidence is reduced due to the empty description.

From the tool's definition Tool name 'create_dns_check' suggests creation of a DNS monitoring check. Description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dns_check Rate-limited

create_dns_check stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dns_check": {
      "limits": [
        {
          "counter": "create_dns_check_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about create_dns_check

What does the create_dns_check tool do? +

create_dns_check. It is categorised as a Write tool in the Pingera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dns_check? +

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

What risk level is create_dns_check? +

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

Can I rate-limit create_dns_check? +

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

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

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