get_account_status
Возвращает статус блокировки аккаунта и настройки уведомлений. Используй для диагностики 'почему API не отвечает' (возможна блокировка при недостатке средств).
This record as markdown: /tools/timeweb-mcp/get-account-status.md
What get_account_status does on Timeweb
AI agents call get_account_status to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_account_status is rated Low
This tool retrieves account metadata (blocking status, notification settings) for diagnostic purposes. It has no side effects, does not modify data, and does not execute operations or commit financial transactions. It is a pure Read operation with minimal blast radius—only exposing account status information that could inform an agent's decision-making but carries no direct risk of data loss or unintended actions.
From the tool's definition Tool name 'get_account_status' and description 'Returns account blocking status and notification settings' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_account_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_account_status, this is the rule to start with:
get_account_status 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 Timeweb, apply this rule, and every get_account_status call is checked against it from then on.
Questions about get_account_status
Возвращает статус блокировки аккаунта и настройки уведомлений. Используй для диагностики 'почему API не отвечает' (возможна блокировка при недостатке средств). It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
Register the Timeweb MCP server in PolicyLayer and add a rule for get_account_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 Timeweb. Nothing to install.
get_account_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_account_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_account_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_account_status is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue