delete_named_semantic_metadata_for_tensor

Delete a named piece of semantic metadata for a given tensor descriptor.

Server Tensorus MCP tensorus/mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_named_semantic_metadata_for_tensor does on Tensorus MCP

AI agents call delete_named_semantic_metadata_for_tensor to permanently remove resources in Tensorus MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_named_semantic_metadata_for_tensor needs a policy

The tool permanently removes semantic metadata from tensors. Although metadata is often less critical than the underlying data, deletion is irreversible and could break downstream dependencies, analytics, or data lineage. This qualifies as Destructive rather than Write because the operation cannot be undone (no undo/restore mechanism mentioned).

From the tool's definition Tool name contains 'delete' and description states 'Delete a named piece of semantic metadata for a given tensor descriptor.' The action is irreversible.

Questions about delete_named_semantic_metadata_for_tensor

What does the delete_named_semantic_metadata_for_tensor tool do? +

Delete a named piece of semantic metadata for a given tensor descriptor. It is categorised as a Destructive tool in the Tensorus MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_named_semantic_metadata_for_tensor? +

Register the Tensorus MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_named_semantic_metadata_for_tensor? +

delete_named_semantic_metadata_for_tensor is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_named_semantic_metadata_for_tensor? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_named_semantic_metadata_for_tensor completely? +

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

What MCP server provides delete_named_semantic_metadata_for_tensor? +

delete_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.