dynamic_tool_func · ikaliMCP Server MCP: Risk & Policy

WHAT IT DOES

What dynamic_tool_func does on ikaliMCP Server

AI agents invoke dynamic_tool_func to trigger actions in ikaliMCP 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 IT NEEDS A POLICY

Why dynamic_tool_func needs a policy

The description is empty, which significantly lowers confidence. However, the server context is a penetration testing toolkit running Kali Linux tools in Docker. Given the sibling tools (bruteforce, SQL injection, exploit search, password cracking, port scanning), a 'dynamic_tool_func' on this server almost certainly executes some form of offensive security operation.

From the tool's definition Tool name is 'dynamic_tool_func' with empty description, but it exists on a server alongside penetration testing tools like nmap, hydra, sqlmap, nikto, hashcat, and searchsploit.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dynamic_tool_func Rate-limited

dynamic_tool_func 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynamic_tool_func": {
      "limits": [
        {
          "counter": "dynamic_tool_func_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ikaliMCP Server, so you can run agents against it safely.

FAQ

Questions about dynamic_tool_func

What does the dynamic_tool_func tool do? +

dynamic_tool_func. It is categorised as a Execute tool in the ikaliMCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dynamic_tool_func? +

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

What risk level is dynamic_tool_func? +

dynamic_tool_func is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dynamic_tool_func? +

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

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

dynamic_tool_func is provided by the ikaliMCP Server MCP server (whobcode/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.