// SCAN REPORT

VikingDB

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 29/06/2026

How to control VikingDB ↓

TOOL MAP

What VikingDB exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous VikingDB tools

Write · Medium vikingdb-upsert-information Upsert (update or insert) is a reversible modification operation that creates new records or updates existing ones.

1 of VikingDB's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control VikingDB

PolicyLayer is an MCP gateway — it sits between your AI agents and VikingDB, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "vikingdb-upsert-information": {
    "limits": [
      {
        "counter": "vikingdb-upsert-information_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "vikingdb-collection-intro": {
    "limits": [
      {
        "counter": "vikingdb-collection-intro_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register VikingDB — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON VIKINGDB →

Instant setup, no code required.

FULL CATALOGUE

All 4 VikingDB tools

WRITE 1 tools

Write vikingdb-upsert-information upsert information to vikingdb for later use

READ 3 tools

Read vikingdb-collection-intro introduce the collection of vikingdb Read vikingdb-index-intro introduce the index of vikingdb Read vikingdb-search-information Look up information in VikingDB. Use this tool when you need to: \n

FAQ

Questions about VikingDB

How do I prevent bulk modifications through VikingDB? +

The VikingDB server has 1 write tools including vikingdb-upsert-information. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach VikingDB.

How many tools does the VikingDB MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on VikingDB? +

Register the VikingDB MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every VikingDB tool call.

Deterministic rules across all 4 VikingDB tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON VIKINGDB →

Instant setup, no code required.

4 VikingDB tools catalogued and risk-classified — across an index of 43,000+ MCP servers.