임의의 MOLD API 명령을 호출합니다. (command + params)
AI agents invoke mold_call_debug to trigger actions in ABLESTACK MOLD MCP 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.
This tool executes arbitrary API commands against cloud infrastructure. Since it can invoke any API (including destructive, financial, or state-changing operations), it spans the most severe categories.
From the tool's definition '임의의 MOLD API 명령을 호출합니다' (calls arbitrary MOLD API commands) with 'command + params' — executes any CloudStack API call
Attacks that exploit this kind of access
임의의 MOLD API 명령을 호출합니다. (command + params). It is categorised as a Execute tool in the ABLESTACK MOLD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ABLESTACK MOLD MCP Server MCP server in PolicyLayer and add a rule for mold_call_debug: 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 ABLESTACK MOLD MCP Server. Nothing to install.
mold_call_debug is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mold_call_debug 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 mold_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.
mold_call_debug is provided by the ABLESTACK MOLD MCP Server MCP server (ycyun/ablestack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
mold_call_debug is one line of ABLESTACK MOLD MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →