flush_server_dns
Flush the DNS cache for a server.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/flush-server-dns.md
What flush_server_dns does on Unofficial FortiMonitor MCP Server
AI agents invoke flush_server_dns to trigger actions in Unofficial FortiMonitor MCP Server. 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.
Why flush_server_dns is rated High
Flushing DNS cache is an operational action that triggers an external operation on a server (clearing its DNS cache), which can affect name resolution behavior. It's not a simple read, nor does it permanently delete data, but it executes a system-level operation with potential service impact if misused.
From the tool's definition Flush the DNS cache for a server
Attacks that exploit this kind of access
The rule that runs flush_server_dns safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flush_server_dns, this is the rule to start with:
flush_server_dns 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every flush_server_dns call is checked against it from then on.
Questions about flush_server_dns
Flush the DNS cache for a server. It is categorised as a Execute tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for flush_server_dns: 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 Unofficial FortiMonitor MCP Server. Nothing to install.
flush_server_dns 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 flush_server_dns 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 flush_server_dns. 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.
flush_server_dns is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.
Across the catalogue