This record as markdown: /tools/ikuai-mcp-server/delete-port-mapping.md
What delete_port_mapping does on Ikuai
AI agents call delete_port_mapping 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_port_mapping is rated Critical
This tool permanently removes port mapping rules from the router, which cannot be undone without manual reconfiguration. Port mappings are critical network infrastructure configurations. Unauthorized deletion could disrupt legitimate service access and network operations. This is irreversible data destruction, making it Destructive rather than Write.
From the tool's definition Tool name 'delete_port_mapping' with description '删除端口映射' (delete port mapping). The verb 'delete' indicates irreversible removal of network configuration data.
Attacks that exploit this kind of access
The rule that runs delete_port_mapping safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ikuai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_port_mapping, this is the rule to start with:
delete_port_mapping is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ikuai, apply this rule, and every delete_port_mapping call is checked against it from then on.
Questions about delete_port_mapping
删除端口映射. 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.
Register the Ikuai MCP server in PolicyLayer and add a rule for delete_port_mapping: 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.
delete_port_mapping is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_port_mapping 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 delete_port_mapping. 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.
delete_port_mapping 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.
Across the catalogue