import_tensor_metadata · Tensorus MCP: Risk & Policy

WHAT IT DOES

What import_tensor_metadata does on Tensorus MCP

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

WHY IT NEEDS A POLICY

Why import_tensor_metadata needs a policy

The tool creates or modifies metadata records in the tensor database. The overwrite strategy indicates reversible modification of existing data (not deletion), placing it in the Write category rather than Destructive.

From the tool's definition Tool description states 'Import tensor metadata' with 'conflict strategy (skip or overwrite)' — this modifies existing metadata reversibly via overwrite or skip strategies.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_tensor_metadata Rate-limited

import_tensor_metadata 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": {
    "import_tensor_metadata": {
      "limits": [
        {
          "counter": "import_tensor_metadata_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 Tensorus MCP, so you can run agents against it safely.

FAQ

Questions about import_tensor_metadata

What does the import_tensor_metadata tool do? +

Import tensor metadata with a specified conflict strategy (skip or overwrite). It is categorised as a Write tool in the Tensorus 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 import_tensor_metadata? +

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

What risk level is import_tensor_metadata? +

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

Can I rate-limit import_tensor_metadata? +

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

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

import_tensor_metadata is provided by the Tensorus MCP server (tensorus/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

import_tensor_metadata is one line of Tensorus's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →