List all versions for a given tensor.
AI agents call list_tensor_versions to retrieve information from Tensorus MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version history information about a tensor—a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal; an agent could only discover metadata about tensor versions, not alter or delete anything.
From the tool's definition Tool name 'list_tensor_versions' and description 'List all versions for a given tensor' indicate a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all versions for a given tensor. It is categorised as a Read tool in the Tensorus MCP MCP Server, which means it retrieves data without modifying state.
Register the Tensorus MCP server in PolicyLayer and add a rule for list_tensor_versions: 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.
list_tensor_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_tensor_versions 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 list_tensor_versions. 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.
list_tensor_versions 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 →