vikingdb-upsert-information · VikingDB MCP: Risk & Policy

WHAT IT DOES

What vikingdb-upsert-information does on VikingDB

AI agents use vikingdb-upsert-information to create or update resources in VikingDB — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VikingDB environment.

WHY IT NEEDS A POLICY

Why vikingdb-upsert-information needs a policy

Upsert (update or insert) is a reversible modification operation that creates new records or updates existing ones. This is characteristic of Write operations. Severity is medium because unintended upserts could pollute the data store with incorrect information, but the operation is reversible through subsequent overwrites or deletes.

From the tool's definition Tool description states 'upsert information to vikingdb' — upsert is a standard write operation that creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vikingdb-upsert-information Rate-limited

vikingdb-upsert-information 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": {
    "vikingdb-upsert-information": {
      "limits": [
        {
          "counter": "vikingdb-upsert-information_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 VikingDB, so you can run agents against it safely.

FAQ

Questions about vikingdb-upsert-information

What does the vikingdb-upsert-information tool do? +

upsert information to vikingdb for later use. It is categorised as a Write tool in the VikingDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vikingdb-upsert-information? +

Register the VikingDB MCP server in PolicyLayer and add a rule for vikingdb-upsert-information: 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 VikingDB. Nothing to install.

What risk level is vikingdb-upsert-information? +

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

Can I rate-limit vikingdb-upsert-information? +

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

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

vikingdb-upsert-information is provided by the VikingDB MCP server (kashiwabyte/vikingdb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.