New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_dhcp_static_binding

删除 DHCP 静态分配

SERVERIkuai SOURCEgxxHuang/ikuai-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ikuai-mcp-server/delete-dhcp-static-binding.md

What delete_dhcp_static_binding does on Ikuai

AI agents call delete_dhcp_static_binding to permanently remove resources in Ikuai, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_dhcp_static_binding is rated Critical

This tool permanently removes DHCP static binding entries, which is a destructive operation that cannot be easily undone. Deleting static bindings could disrupt network connectivity for specific devices that rely on fixed IP assignments, causing service interruption. The action is irreversible and would require manual reconfiguration to restore.

From the tool's definition Tool name contains 'delete_dhcp_static_binding' and description states '删除 DHCP 静态分配' (delete DHCP static binding). The verb '删除' means 'delete' in Chinese, indicating irreversible removal of network configuration data.

Questions about delete_dhcp_static_binding

What does the delete_dhcp_static_binding tool do? +

删除 DHCP 静态分配. It is categorised as a Destructive tool in the Ikuai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_dhcp_static_binding? +

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

What risk level is delete_dhcp_static_binding? +

delete_dhcp_static_binding is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_dhcp_static_binding? +

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

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

delete_dhcp_static_binding is provided by the Ikuai MCP server (gxxHuang/ikuai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ikuai, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ikuai's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.