ows_register_identity · Execution Market MCP: Risk & Policy

WHAT IT DOES

What ows_register_identity does on Execution Market

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

WHY IT NEEDS A POLICY

Why ows_register_identity needs a policy

Registration of an identity is a state-modifying operation that creates a new on-chain entity. While gasless and reversible in principle (identity could theoretically be deregistered), it commits the wallet to a persistent blockchain record. This is a Write operation rather than Read (which would only query identity state) or Execute/Destructive (no code execution or deletion).

From the tool's definition Tool description states 'Register an ERC-8004 on-chain identity' — this creates a new on-chain record tied to the caller's wallet. The term 'Register' indicates a creation/initialization action that modifies blockchain state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ows_register_identity Rate-limited

ows_register_identity 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": {
    "ows_register_identity": {
      "limits": [
        {
          "counter": "ows_register_identity_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 Execution Market, so you can run agents against it safely.

FAQ

Questions about ows_register_identity

What does the ows_register_identity tool do? +

Register an ERC-8004 on-chain identity for your wallet — completely gasless. It is categorised as a Write tool in the Execution Market MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ows_register_identity? +

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

What risk level is ows_register_identity? +

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

Can I rate-limit ows_register_identity? +

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

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

ows_register_identity is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.