Create a relationship between two entities (feature, file, test, issue, decision).
AI agents use cortex_add_relationship to create or update resources in Cortex MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cortex MCP environment.
The tool writes data (relationship records) in a structured knowledge store but does not execute arbitrary code, delete data, move money, or trigger uncontrolled external operations. The impact is limited to the internal memory/knowledge graph of the Cortex system.
From the tool's definition Tool creates relationships between entities by design ('Create a relationship between two entities'). This is a reversible data modification operation that adds metadata linking existing entities without altering their content or triggering external side…
Attacks that exploit this kind of access
Create a relationship between two entities (feature, file, test, issue, decision). It is categorised as a Write tool in the Cortex MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_add_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 Cortex MCP. Nothing to install.
cortex_add_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 cortex_add_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 cortex_add_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.
cortex_add_relationship is provided by the Cortex MCP server (neuralnexustech/cortex-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 →