domain_bindings_dns_plan
Read domain-bindings.dns-plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/domain-bindings-dns-plan.md
What domain_bindings_dns_plan does on Appaloft
AI agents call domain_bindings_dns_plan to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ttl | integer | — | |
proxied | boolean | — | |
zoneName | string | — | |
recordType | string | — | |
connectorKey | string | — | |
capabilityKey | string | — | |
domainBindingId | string | Yes |
Parameters from the server's own tool schema.
Why domain_bindings_dns_plan is rated Low
The tool explicitly states it reads DNS plan information for domain bindings. This is a data retrieval operation with no side effects. The word 'Read' is used directly in the description.
From the tool's definition "Read domain-bindings.dns-plan through the Appaloft application operation catalog"
Attacks that exploit this kind of access
The rule that runs domain_bindings_dns_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_bindings_dns_plan, this is the rule to start with:
domain_bindings_dns_plan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every domain_bindings_dns_plan call is checked against it from then on.
Questions about domain_bindings_dns_plan
Read domain-bindings.dns-plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
domain_bindings_dns_plan accepts 7 parameters: ttl, proxied, zoneName, recordType, connectorKey, capabilityKey, domainBindingId. Required: domainBindingId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for domain_bindings_dns_plan: 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 Appaloft. Nothing to install.
domain_bindings_dns_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the domain_bindings_dns_plan 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.
Set action: deny in the PolicyLayer policy for domain_bindings_dns_plan. 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.
domain_bindings_dns_plan is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue