update_tensor_descriptor · Tensorus MCP: Risk & Policy

WHAT IT DOES

What update_tensor_descriptor does on Tensorus MCP

AI agents use update_tensor_descriptor 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 update_tensor_descriptor needs a policy

This tool modifies tensor descriptors (metadata about tensors) in a reversible manner. Updates are typical Write operations—they change state but can be undone by subsequent updates.

From the tool's definition Tool name 'update_tensor_descriptor' and description 'Update a tensor descriptor by its ID' indicate modification of existing metadata/configuration rather than data deletion or irreversible destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tensor_descriptor Rate-limited

update_tensor_descriptor 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": {
    "update_tensor_descriptor": {
      "limits": [
        {
          "counter": "update_tensor_descriptor_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 update_tensor_descriptor

What does the update_tensor_descriptor tool do? +

Update a tensor descriptor by its ID. 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 update_tensor_descriptor? +

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

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

Can I rate-limit update_tensor_descriptor? +

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

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

update_tensor_descriptor 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

update_tensor_descriptor 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 →