Retrieve tensor data and metadata.
AI agents call tensorus_get_tensor_details 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 or queries existing tensor data and metadata without side effects. It does not create, modify, delete, or execute operations—it simply fetches information. This is a classic Read operation with minimal risk if misused by an AI agent, as the worst outcome would be unauthorized access to data already in the system.
From the tool's definition Tool name 'tensorus_get_tensor_details' and description 'Retrieve tensor data and metadata' indicate a read-only query operation with no modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
Retrieve tensor data and metadata. 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 tensorus_get_tensor_details: 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_get_tensor_details 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 tensorus_get_tensor_details 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_get_tensor_details. 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_get_tensor_details 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 →