create_dashboard_direct · Insight Digger MCP: Risk & Policy

WHAT IT DOES

What create_dashboard_direct does on Insight Digger MCP

AI agents use create_dashboard_direct to create or update resources in Insight Digger MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Insight Digger MCP environment.

WHY IT NEEDS A POLICY

Why create_dashboard_direct needs a policy

The tool performs a create operation that results in new persistent dashboard artifacts. This falls under Write (creates or modifies data reversibly) rather than Execute, since dashboard creation is a structured data modification operation, not arbitrary code execution.

From the tool's definition Tool creates dashboards (creates/modifies data) from JSON config. The description explicitly states 'Create dashboard directly' and emphasizes it as a one-shot creation method with caching, indicating persistent data modification rather than temporary…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dashboard_direct Rate-limited

create_dashboard_direct stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dashboard_direct": {
      "limits": [
        {
          "counter": "create_dashboard_direct_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Insight Digger MCP, so you can run agents against it safely.

FAQ

Questions about create_dashboard_direct

What does the create_dashboard_direct tool do? +

🚀 Create dashboard directly from question using JSON config - ONE-SHOT, NO MARKDOWN! This is the FASTEST way to create dashboards with FILTERS PRESERVED. 🔄 Auto-Cached:. It is categorised as a Write tool in the Insight Digger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dashboard_direct? +

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

What risk level is create_dashboard_direct? +

create_dashboard_direct is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_dashboard_direct? +

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

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

create_dashboard_direct is provided by the Insight Digger MCP server (sandsiv/data_narrator_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.