updown_paused
Check if an UPDOWN asset is paused (writes will revert if true).
This record as markdown: /tools/launch-on-basis-mcp-ts/updown-paused.md
What updown_paused does on Basis MCP Server
AI agents call updown_paused to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why updown_paused is rated Low
This tool reads the paused status of an UPDOWN asset and returns that information. It performs no side effects, creates no transactions, and modifies no state. It is a simple state query, falling squarely into the Read category with low severity since misuse would only retrieve information without affecting any blockchain state or assets.
From the tool's definition The tool description states 'Check if an UPDOWN asset is paused', which is a query operation that retrieves status information. The phrase 'writes will revert if true' describes a consequence of the paused state, not an action this tool performs.
Attacks that exploit this kind of access
The rule that runs updown_paused safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updown_paused, this is the rule to start with:
updown_paused is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every updown_paused call is checked against it from then on.
Questions about updown_paused
Check if an UPDOWN asset is paused (writes will revert if true). It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for updown_paused: 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 Basis MCP Server. Nothing to install.
updown_paused 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 updown_paused 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 updown_paused. 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.
updown_paused is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue