acknowledge-packet · Osmosis MCP Server MCP: Risk & Policy

WHAT IT DOES

What acknowledge-packet does on Osmosis MCP Server

AI agents invoke acknowledge-packet 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 acknowledge-packet needs a policy

Acknowledging an IBC packet is an on-chain transaction that changes the state of an Inter-Blockchain Communication protocol packet. While it sounds like a confirmation step, it executes a blockchain transaction with real effects on cross-chain state. It cannot be trivially undone once submitted, and misuse could affect cross-chain asset transfers or messages.

From the tool's definition Acknowledge receipt of an IBC packet — triggers an external blockchain operation (IBC protocol acknowledgment) that finalizes cross-chain packet state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

acknowledge-packet Rate-limited

acknowledge-packet 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": {
    "acknowledge-packet": {
      "limits": [
        {
          "counter": "acknowledge-packet_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 acknowledge-packet

What does the acknowledge-packet tool do? +

Acknowledge receipt of an IBC packet. 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 acknowledge-packet? +

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

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

Can I rate-limit acknowledge-packet? +

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

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

acknowledge-packet 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.