dual_update_object · DUAL MCP Server MCP: Risk & Policy

WHAT IT DOES

What dual_update_object does on DUAL MCP Server

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

WHY IT NEEDS A POLICY

Why dual_update_object needs a policy

This tool modifies properties of tokenized objects on a blockchain system, which constitutes a Write operation. While the changes are reversible (can be updated again), the high severity reflects that tokenized objects likely represent digital assets with value on a Web3 system, making unauthorized or erroneous updates potentially high-impact to users or organizations managing those assets.

From the tool's definition Tool name 'dual_update_object' and description 'Update the properties of a tokenized object' indicates modification of existing data. The qualifier 'Only mutable properties can be changed' confirms reversible writes rather than destructive operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dual_update_object Rate-limited

dual_update_object 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dual_update_object": {
      "limits": [
        {
          "counter": "dual_update_object_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DUAL MCP Server, so you can run agents against it safely.

FAQ

Questions about dual_update_object

What does the dual_update_object tool do? +

Update the properties of a tokenized object. Only mutable properties can be changed. It is categorised as a Write tool in the DUAL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dual_update_object? +

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

What risk level is dual_update_object? +

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

Can I rate-limit dual_update_object? +

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

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

dual_update_object is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.