// MCP TOOL REFERENCE

function_call_debug

Debug function calling issues via DeepSeek

Sends tool definitions to external API

Part of the Deepseek MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@arikusi/deepseek-mcp-server Execute Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke function_call_debug to trigger processes or run actions in Deepseek. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON FUNCTION_CALL_DEBUG

function_call_debug can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-arikusi-deepseek.yaml

tools:
  function_call_debug:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Deepseek policy for all 15 tools.

// DETAILS

Tool Name function_call_debug

Category Execute

MCP Server Deepseek MCP Server

Risk Level High

// MORE DEEPSEEK TOOLS

Execute argument_validation Execute code_review_deep Execute create_function_schema Execute creative_ideation Execute debug_with_reasoning Execute explain_like_im_five Execute mathematical_proof Execute pair_programming

View all 15 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like function_call_debug have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

function_call_debug is one of the high-risk operations in Deepseek. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the function_call_debug tool do? +

Debug function calling issues via DeepSeek. It is categorised as a Execute tool in the Deepseek MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on function_call_debug? +

Add a rule in your Intercept YAML policy under the tools section for function_call_debug. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Deepseek MCP server.

What risk level is function_call_debug? +

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

Can I rate-limit function_call_debug? +

Yes. Add a rate_limit block to the function_call_debug rule in your Intercept 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 function_call_debug completely? +

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

function_call_debug is provided by the Deepseek MCP server (@arikusi/deepseek-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

function_call_debug

Enforce policies on Deepseek