analytics_get_complex_tensors

Get complex tensors based on minimum parent count, transformation steps, and limit.

Server Tensorus MCP tensorus/mcp
Category Read
Risk class Low
Parameters 00 required

What analytics_get_complex_tensors does on Tensorus MCP

AI agents call analytics_get_complex_tensors 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.

Why analytics_get_complex_tensors needs a policy

This is a query/retrieval operation that filters and returns tensor data. The verb 'Get' and the analytics context indicate data retrieval only. There is no indication of data creation, modification, deletion, code execution, or financial operations. The filtering parameters (minimum parent count, transformation steps, limit) are all read-only query constraints.

From the tool's definition Tool name contains 'analytics_get' and description states 'Get complex tensors' - retrieves data based on filtering criteria (parent count, transformation steps, limit) with no modification or side effects.

Questions about analytics_get_complex_tensors

What does the analytics_get_complex_tensors tool do? +

Get complex tensors based on minimum parent count, transformation steps, and limit. It is categorised as a Read tool in the Tensorus MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analytics_get_complex_tensors? +

Register the Tensorus MCP server in PolicyLayer and add a rule for analytics_get_complex_tensors: 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 analytics_get_complex_tensors? +

analytics_get_complex_tensors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analytics_get_complex_tensors? +

Yes. Add a rate_limit block to the analytics_get_complex_tensors 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 analytics_get_complex_tensors completely? +

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

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