update-client · Osmosis MCP Server MCP: Risk & Policy

WHAT IT DOES

What update-client does on Osmosis MCP Server

AI agents invoke update-client to trigger actions in Osmosis MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why update-client needs a policy

Updating an IBC light client submits a blockchain transaction that modifies on-chain state for cross-chain communication. This is not a simple write since it involves executing a transaction on the Osmosis blockchain with external effects; misuse could disrupt IBC connections and cross-chain operations, justifying high severity.

From the tool's definition 'Update an IBC light client with new header' - triggers an external blockchain transaction that modifies state of an IBC light client

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-client Rate-limited

update-client stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-client": {
      "limits": [
        {
          "counter": "update-client_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about update-client

What does the update-client tool do? +

Update an IBC light client with new header. It is categorised as a Execute tool in the Osmosis MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on update-client? +

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

What risk level is update-client? +

update-client is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit update-client? +

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

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

update-client is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.