cosmos_tx · Manifest MCP: Risk & Policy

WHAT IT DOES

What cosmos_tx does on Manifest MCP

AI agents invoke cosmos_tx to trigger actions in Manifest MCP. 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 cosmos_tx needs a policy

This tool executes arbitrary blockchain transactions on Cosmos SDK chains. While not inherently destructive (transactions are reversible via blockchain mechanics), the capability to 'execute any' transaction with automatic signing means an AI agent could transfer funds, modify on-chain state, or trigger irreversible contract calls based on user prompts or injected instructions.

From the tool's definition Tool description states 'Execute any Cosmos SDK transaction with automatic signing and gas estimation.' The verb 'Execute' combined with 'any Cosmos SDK transaction' with automatic signing indicates the tool runs external operations (blockchain transactions)…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cosmos_tx Rate-limited

cosmos_tx 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": {
    "cosmos_tx": {
      "limits": [
        {
          "counter": "cosmos_tx_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 Manifest MCP, so you can run agents against it safely.

FAQ

Questions about cosmos_tx

What does the cosmos_tx tool do? +

Execute any Cosmos SDK transaction with automatic signing and gas estimation. Call list_modules and list_module_subcommands first to discover available options. It is categorised as a Execute tool in the Manifest MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cosmos_tx? +

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

What risk level is cosmos_tx? +

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

Can I rate-limit cosmos_tx? +

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

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

cosmos_tx is provided by the Manifest MCP server (manifest-network/manifest-mcp-mono). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.