Medium Risk

update_entity_relationship

Update entity relationship (PATCH semantics - only provided fields changed). WHEN: Refining relationship details after creation: - Updating strength/confidence based on new information - Adding metadata (verification dates, additional context) - Changing relationship type BEHAVIOR: Only provided ...

How to control update_entity_relationship ↓

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

Medium Risk

This is a Write operation because it creates or modifies data in a reversible manner. PATCH semantics indicate selective field updates rather than destructive replacement. The tool allows refinement of relationship metadata without irreversible deletion. Severity is medium because misuse could corrupt knowledge base relationships and integrity, but changes are reversible via subsequent updates.

From the tool's definition Tool description explicitly states "Update entity relationship (PATCH semantics - only provided fields changed)" and lists update operations: "Updating strength/confidence based on new information, Adding metadata (verification dates, additional context),…

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

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

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

update_entity_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 Forgetful — 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 update_entity_relationship tool do? +

Update entity relationship (PATCH semantics - only provided fields changed). WHEN: Refining relationship details after creation: - Updating strength/confidence based on new information - Adding metadata (verification dates, additional context) - Changing relationship type BEHAVIOR: Only provided arguments are updated. Null/omitted arguments leave the field unchanged. Returns updated relationship with new timestamps. Args: relationship_id: Relationship ID to update relationship_type: New type (unchanged if omitted) strength: New strength (unchanged if omitted) confidence: New confidence (unchanged if omitted) metadata: New metadata dict (unchanged if omitted, replaces if provided) ctx: Context (automatically injected) Returns: Updated EntityRelationship with new timestamps Raises: ToolError: If relationship not found or validation fails. It is categorised as a Write tool in the Forgetful MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_entity_relationship? +

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

What risk level is update_entity_relationship? +

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

Can I rate-limit update_entity_relationship? +

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

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

update_entity_relationship is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Forgetful tool call.

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

Free to start. No card required.

59 Forgetful 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.