debug_function

Run JS code in debug mode (without deploying). Returns execution result and console logs

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/debug-function.md

WHAT IT DOES

What debug_function does on Webcake Storefront

AI agents invoke debug_function to trigger actions in Webcake Storefront. 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.

RISK

Why debug_function is rated High

This tool allows execution of arbitrary JavaScript code, making it an Execute-category risk. While it operates in 'debug mode' without deploying, it still runs code and returns results, which could be leveraged to access sensitive data, enumerate the system, or probe for vulnerabilities.

From the tool's definition The tool explicitly states it will 'Run JS code in debug mode' and 'Returns execution result and console logs'. This permits arbitrary JavaScript execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debug_function safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debug_function, this is the rule to start with:

debug_function Rate-limited

debug_function 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": {
    "debug_function": {
      "limits": [
        {
          "counter": "debug_function_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every debug_function call is checked against it from then on.

FAQ

Questions about debug_function

What does the debug_function tool do? +

Run JS code in debug mode (without deploying). Returns execution result and console logs. It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debug_function? +

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

What risk level is debug_function? +

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

Can I rate-limit debug_function? +

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

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

debug_function is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools → High-risk tools on this server →

Across the catalogue

hook_function on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →