Medium Risk

update_relationship_value

Update a relationship value and/or metadata. Use mode

How to control update_relationship_value ↓

What update_relationship_value does on DMCP

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

Medium Risk

Why update_relationship_value needs a policy

This tool modifies game state (relationship values and metadata) but does so reversibly—relationships can be updated again or reset. There is no irreversible deletion, code execution, financial impact, or external system triggering.

From the tool's definition Tool name 'update_relationship_value' and description 'Update a relationship value and/or metadata' indicate modification of existing game state data.

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

How to control update_relationship_value

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

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

update_relationship_value 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 DMCP — 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.

Related tools and policies

Go deeper

Questions about update_relationship_value

What does the update_relationship_value tool do? +

Update a relationship value and/or metadata. Use mode. It is categorised as a Write tool in the DMCP 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_relationship_value? +

Register the D MCP server in PolicyLayer and add a rule for update_relationship_value: 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 DMCP. Nothing to install.

What risk level is update_relationship_value? +

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

Can I rate-limit update_relationship_value? +

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

Set action: deny in the PolicyLayer policy for update_relationship_value. 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_relationship_value? +

update_relationship_value is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DMCP tool call.

Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

204 DMCP tools catalogued and risk-classified — across an index of 43,000+ 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.