Replace metadata for a specific tensor.
AI agents use tensorus_update_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.
This tool modifies tensor metadata in a database. It is Write-category because it creates or modifies data reversibly—metadata can be updated again or reverted. It is not Destructive because replacement of metadata is not irreversible in a typical database context (previous states can often be recovered or re-updated).
From the tool's definition Tool name 'update_tensor_metadata' and description 'Replace metadata for a specific tensor' indicate modification of existing data. The word 'Replace' suggests reversible update operations on tensor metadata.
Attacks that exploit this kind of access
Replace metadata for a specific tensor. 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.
Register the Tensorus MCP server in PolicyLayer and add a rule for tensorus_update_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.
tensorus_update_tensor_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tensorus_update_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.
Set action: deny in the PolicyLayer policy for tensorus_update_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.
tensorus_update_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →