Medium Risk

create_knowledge_relationship

Create a relationship between two entities in the knowledge graph

How to control create_knowledge_relationship ↓

AI agents use create_knowledge_relationship to create or update resources in ZMCPTools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZMCPTools environment.

Medium Risk

The tool creates new relationships between entities in a knowledge graph, which is a write operation that modifies the knowledge graph state. It does not execute arbitrary code, delete data, or move financial resources. While it modifies data, the operation is reversible (relationships can be removed).

From the tool's definition Tool name 'create_knowledge_relationship' and description 'Create a relationship between two entities in the knowledge graph' indicate creation of new data structures in a knowledge graph system. This is a reversible modification operation.

Documented attack patterns abuse exactly the kind of access create_knowledge_relationship gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for create_knowledge_relationship:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_knowledge_relationship": {
      "limits": [
        {
          "counter": "create_knowledge_relationship_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_knowledge_relationship stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ZMCPTools — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the create_knowledge_relationship tool do? +

Create a relationship between two entities in the knowledge graph. It is categorised as a Write tool in the ZMCPTools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_knowledge_relationship? +

Register the ZMCPTools MCP server in PolicyLayer and add a rule for create_knowledge_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 ZMCPTools. Nothing to install.

What risk level is create_knowledge_relationship? +

create_knowledge_relationship is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_knowledge_relationship? +

Yes. Add a rate_limit block to the create_knowledge_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.

How do I block create_knowledge_relationship completely? +

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

What MCP server provides create_knowledge_relationship? +

create_knowledge_relationship is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ZMCPTools tool call.

Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.