validate_settings · Insight Digger MCP: Risk & Policy

WHAT IT DOES

What validate_settings does on Insight Digger MCP

AI agents invoke validate_settings to trigger actions in Insight Digger MCP. 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 validate_settings needs a policy

This tool executes a live connection test against an external API, which constitutes an external operation with real network side effects. It is not a pure read (no data is retrieved for user consumption) nor a write (no data is persisted), but it does trigger an external operation whose effects depend on the provided arguments (apiUrl, jwtToken).

From the tool's definition 'Validate API settings by testing the connection to the external data API' — the tool actively triggers an outbound network connection to an external API endpoint

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

validate_settings Rate-limited

validate_settings 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": {
    "validate_settings": {
      "limits": [
        {
          "counter": "validate_settings_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 Insight Digger MCP, so you can run agents against it safely.

FAQ

Questions about validate_settings

What does the validate_settings tool do? +

Validate API settings by testing the connection to the external data API. 🔄 Auto-Cached: apiUrl and jwtToken are automatically provided from your authentication session - you typically don. It is categorised as a Execute tool in the Insight Digger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on validate_settings? +

Register the Insight Digger MCP server in PolicyLayer and add a rule for validate_settings: 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 validate_settings? +

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

Can I rate-limit validate_settings? +

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

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

validate_settings 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.