Ingest a new tensor into a dataset.
AI agents use tensorus_ingest_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 creates or adds new tensor data to a dataset, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or transfer funds (Financial). The severity is medium because uncontrolled tensor ingestion could consume storage resources or corrupt dataset integrity, but the operation is reversible.
From the tool's definition Tool name 'tensorus_ingest_tensor' and description 'Ingest a new tensor into a dataset' indicate creation of new data within the tensor database. 'Ingest' is a data insertion operation that modifies dataset state.
Attacks that exploit this kind of access
Ingest a new tensor into a dataset. 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 tensorus_ingest_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.
tensorus_ingest_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 tensorus_ingest_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 tensorus_ingest_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.
tensorus_ingest_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 →