Create a lineage relationship between tensors.
AI agents use create_lineage_relationship 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 new metadata relationships (lineage connections) between existing tensors. This is a Write operation: it modifies the database state by adding relational records, but the change is reversible (relationships can be deleted or updated). It does not execute arbitrary code (Execute), irreversibly delete data (Destructive), or involve financial transactions.
From the tool's definition Tool name contains 'create' and description states 'Create a lineage relationship between tensors'—a reversible data modification operation that establishes metadata links.
Attacks that exploit this kind of access
Create a lineage relationship between tensors. 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 create_lineage_relationship: 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.
create_lineage_relationship 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 create_lineage_relationship 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 create_lineage_relationship. 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.
create_lineage_relationship 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 →