Download and install a DNS app from the Technitium app store. Use dns_list_app_store to see available apps.
AI agents invoke dns_install_app to trigger actions in Technitium MCP Secure. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool downloads and installs software onto the DNS server, which constitutes execution of an external operation that modifies the server's software environment. Installing apps can introduce new functionality, change server behavior, or create security risks.
From the tool's definition Download and install a DNS app from the Technitium app store
Documented attack patterns abuse exactly the kind of access dns_install_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Technitium MCP Secure, and nothing reaches the server without passing your rules. This is the rule we recommend for dns_install_app:
{
"version": "1",
"default": "deny",
"tools": {
"dns_install_app": {
"limits": [
{
"counter": "dns_install_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} dns_install_app stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Download and install a DNS app from the Technitium app store. Use dns_list_app_store to see available apps. It is categorised as a Execute tool in the Technitium MCP Secure MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Technitium MCP Secure MCP server in PolicyLayer and add a rule for dns_install_app: 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 Technitium MCP Secure. Nothing to install.
dns_install_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dns_install_app 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 dns_install_app. 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.
dns_install_app is provided by the Technitium MCP Secure MCP server (rosschurchill/technitium-mcp-secure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Technitium MCP Secure, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Technitium MCP Secure tools catalogued and risk-classified — across an index of 43,000+ MCP servers.