Low Risk

get_error_details

Get full error details for a prompt (node_id, exception_type, exception_message, full traceback). Use when execute_workflow_sync failed or get_execution_status shows errors. Returns structured errors from ComfyUI history status.messages. Requires COMFYUI_HOST.

Part of the ComfyUI Builder server.

get_error_details is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE COMFYUI BUILDER →

Free to start. No card required.

AI agents call get_error_details to retrieve information from ComfyUI Builder without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_error_details only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_error_details": {}
  }
}

See the full ComfyUI Builder policy for all 60 tools.

Get this rule live on your own ComfyUI Builder server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COMFYUI BUILDER →

View all 60 tools →

These attack patterns abuse exactly the kind of access get_error_details gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_error_details only ever does what you allow.

SECURE COMFYUI BUILDER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_error_details tool do? +

Get full error details for a prompt (node_id, exception_type, exception_message, full traceback). Use when execute_workflow_sync failed or get_execution_status shows errors. Returns structured errors from ComfyUI history status.messages. Requires COMFYUI_HOST.. It is categorised as a Read tool in the ComfyUI Builder MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_error_details? +

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

What risk level is get_error_details? +

get_error_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_error_details? +

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

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

get_error_details is provided by the ComfyUI Builder MCP server (mcp-comfy-ui-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ComfyUI Builder tool call.

Deterministic rules across all 60 ComfyUI Builder tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.