get_server_logs
Возвращает лог жизненного цикла сервера: install, reboot, shutdown, reinstall и пр. Полезно для диагностики (почему сервер сейчас в off, когда последний reinstall). Это НЕ application logs и НЕ syslog — только события уровня гипервизора.
This record as markdown: /tools/timeweb-mcp/get-server-logs.md
What get_server_logs does on Timeweb
AI agents call get_server_logs 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
order | string | — | НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - порядок сортировки по дате (по умолчанию: desc — сначала новые) |
server_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сервера |
Parameters from the server's own tool schema.
Why get_server_logs is rated Low
Even though get_server_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_server_logs 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_server_logs, this is the rule to start with:
get_server_logs 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_server_logs call is checked against it from then on.
Questions about get_server_logs
Возвращает лог жизненного цикла сервера: install, reboot, shutdown, reinstall и пр. Полезно для диагностики (почему сервер сейчас в off, когда последний reinstall). Это НЕ application logs и НЕ syslog — только события уровня гипервизора. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
get_server_logs accepts 2 parameters: order, server_id. Required: server_id. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for get_server_logs: 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_server_logs 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_server_logs 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_server_logs. 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_server_logs 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