Returns current downtime status for the chain
AI agents call get-downtime-status 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 retrieves blockchain chain status information with no side effects. It performs a simple data query operation consistent with the 'Read' category (fetch/get operations). The low severity reflects that misuse cannot cause financial loss, data modification, or destructive actions—it only exposes status information already publicly available on the blockchain.
From the tool's definition Tool name 'get-downtime-status' and description 'Returns current downtime status for the chain' indicate a read-only query operation that retrieves status information without modifying state or executing transactions.
Attacks that exploit this kind of access
Returns current downtime status for the chain. 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 get-downtime-status: 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.
get-downtime-status 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 get-downtime-status 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 get-downtime-status. 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.
get-downtime-status 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 →