Validates if a denomination is a valid token factory denom
AI agents call validate-token-factory-denom to retrieve information from Osmosis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation—a read-only operation that checks whether input data conforms to expected criteria. It retrieves or computes information about a denomination without creating, modifying, deleting, or executing transactions. The operation has no side effects on blockchain state, making it a Read category tool with low severity.
From the tool's definition Tool name: 'validate-token-factory-denom'. Description: 'Validates if a denomination is a valid token factory denom'.
Attacks that exploit this kind of access
Validates if a denomination is a valid token factory denom. It is categorised as a Read tool in the Osmosis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for validate-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.
validate-token-factory-denom is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate-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.
Set action: deny in the PolicyLayer policy for validate-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.
validate-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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →