private_loading_start · Claude Imagine MCP: Risk & Policy

WHAT IT DOES

What private_loading_start does on Claude Imagine

AI agents invoke private_loading_start to trigger actions in Claude Imagine. 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 private_loading_start needs a policy

This tool executes a specific action (rendering a loading indicator) on the client browser via the MCP server's WebSocket communication. While the blast radius of misuse is low (it merely shows a visual element with no data modification or command execution), the mechanism—triggering side effects in an external system—places it in Execute rather than Read.

From the tool's definition The tool 'private_loading_start' sends WebSocket commands to update the browser's UI state by showing a global loading bar. This is an action that triggers external visual effects in a browser interface, which aligns with Execute category behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

private_loading_start Rate-limited

private_loading_start 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": {
    "private_loading_start": {
      "limits": [
        {
          "counter": "private_loading_start_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 Claude Imagine, so you can run agents against it safely.

FAQ

Questions about private_loading_start

What does the private_loading_start tool do? +

Show the global loading bar. It is categorised as a Execute tool in the Claude Imagine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on private_loading_start? +

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

What risk level is private_loading_start? +

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

Can I rate-limit private_loading_start? +

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

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

private_loading_start is provided by the Claude Imagine MCP server (t3rm1nu55/claudeimagine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.