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

WHAT IT DOES

What update-params does on Osmosis MCP Server

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

WHY IT NEEDS A POLICY

Why update-params needs a policy

This tool creates or modifies data (module parameters) reversibly through a governance/admin process, fitting the Write category. Although it affects system-wide configuration (elevating severity to 'high' due to blast radius if misused by an unauthorized agent), it is not Destructive (parameters can typically be reverted through governance), not Financial (no money movement), and not Execute (it modifies config,…

From the tool's definition Tool name 'update-params' combined with description stating it updates 'module parameters' with 'governance/admin only' restriction indicates modification of blockchain configuration state.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-params Rate-limited

update-params 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": {
    "update-params": {
      "limits": [
        {
          "counter": "update-params_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 Osmosis MCP Server, so you can run agents against it safely.

FAQ

Questions about update-params

What does the update-params tool do? +

Update module parameters (governance/admin only). It is categorised as a Write tool in the Osmosis 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 update-params? +

Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for update-params: 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-params? +

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

Can I rate-limit update-params? +

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

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

update-params 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.