get_log_stream_history

Get the history for a specific log stream

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/get-log-stream-history.md

WHAT IT DOES

What get_log_stream_history does on Linode MCP Server

AI agents call get_log_stream_history to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_log_stream_history is rated Low

This tool retrieves historical log data without performing any side effects, modifications, or destructive actions. It is a straightforward read operation that queries existing log stream information.

From the tool's definition Tool name 'get_log_stream_history' and description 'Get the history for a specific log stream' indicate data retrieval with no modification or deletion of logs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_log_stream_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_log_stream_history, this is the rule to start with:

get_log_stream_history Allowed

get_log_stream_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_log_stream_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every get_log_stream_history call is checked against it from then on.

FAQ

Questions about get_log_stream_history

What does the get_log_stream_history tool do? +

Get the history for a specific log stream. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_log_stream_history? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for get_log_stream_history: 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 Linode MCP Server. Nothing to install.

What risk level is get_log_stream_history? +

get_log_stream_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_log_stream_history? +

Yes. Add a rate_limit block to the get_log_stream_history 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.

How do I block get_log_stream_history completely? +

Set action: deny in the PolicyLayer policy for get_log_stream_history. 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.

What MCP server provides get_log_stream_history? +

get_log_stream_history is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →