set-send-enabled · Osmosis MCP Server MCP: Risk & Policy

WHAT IT DOES

What set-send-enabled does on Osmosis MCP Server

AI agents use set-send-enabled 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 set-send-enabled needs a policy

This tool modifies blockchain configuration by controlling which tokens can be sent, making it a Write operation. It's classified as 'high' severity because misconfiguration could disable critical token transfers for users, causing operational disruption, though it remains reversible by authorized admins. Confidence is high because the description clearly indicates state modification without irreversibility.

From the tool's definition The tool description states it enables or disables sending for specific token denominations. This is a configuration change that modifies system state (token sending permissions) but is reversible—the admin can re-enable sending later.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set-send-enabled Rate-limited

set-send-enabled 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": {
    "set-send-enabled": {
      "limits": [
        {
          "counter": "set-send-enabled_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 set-send-enabled

What does the set-send-enabled tool do? +

Enable or disable sending for specific token denominations (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 set-send-enabled? +

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

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

Can I rate-limit set-send-enabled? +

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

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

set-send-enabled 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.