Update a named piece of semantic metadata for a given tensor descriptor.
AI agents use update_named_semantic_metadata_for_tensor 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 metadata associated with tensors in the database, which is a reversible write operation. It does not create new tensors, execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states 'Update a named piece of semantic metadata for a given tensor descriptor.' The verb 'update' indicates modification of existing data.
Attacks that exploit this kind of access
Update a named piece of semantic metadata for a given tensor descriptor. 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 update_named_semantic_metadata_for_tensor: 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.
update_named_semantic_metadata_for_tensor 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 update_named_semantic_metadata_for_tensor 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 update_named_semantic_metadata_for_tensor. 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.
update_named_semantic_metadata_for_tensor 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 →