prepare-create-token-factory-denom · Osmosis MCP Server MCP

WHAT IT DOES

What prepare-create-token-factory-denom does on Osmosis MCP Server

AI agents use prepare-create-token-factory-denom 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 prepare-create-token-factory-denom needs a policy

This tool creates a new token factory denomination on the Osmosis blockchain, which is a reversible but significant state modification. It does not execute the transaction immediately (hence Write rather than Execute), does not delete data (not Destructive), does not move funds directly (not Financial), and is not merely a read query (not Read).

From the tool's definition 'Prepares a transaction to create a new token factory denomination' indicates creation of a new on-chain asset/token.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prepare-create-token-factory-denom Rate-limited

prepare-create-token-factory-denom 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": {
    "prepare-create-token-factory-denom": {
      "limits": [
        {
          "counter": "prepare-create-token-factory-denom_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 prepare-create-token-factory-denom

What does the prepare-create-token-factory-denom tool do? +

Prepares a transaction to create a new token factory denomination. 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 prepare-create-token-factory-denom? +

Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for prepare-create-token-factory-denom: 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 prepare-create-token-factory-denom? +

prepare-create-token-factory-denom is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit prepare-create-token-factory-denom? +

Yes. Add a rate_limit block to the prepare-create-token-factory-denom 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 prepare-create-token-factory-denom completely? +

Set action: deny in the PolicyLayer policy for prepare-create-token-factory-denom. 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 prepare-create-token-factory-denom? +

prepare-create-token-factory-denom 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.