Low Risk

list_log_streams

Get a list of all log streams

How to control list_log_streams ↓

What list_log_streams does on Linode MCP Server

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

Low Risk

Why list_log_streams needs a policy

This tool performs a read-only query operation that retrieves log stream metadata. It does not create, modify, delete, execute code, or move money. The blast radius of misuse is minimal—an attacker could only gain visibility into existing logs, which does not compromise system integrity or resources directly.

From the tool's definition Tool name 'list_log_streams' and description 'Get a list of all log streams' indicate retrieval of existing data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access list_log_streams gives an agent:

How to control list_log_streams

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_log_streams:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_log_streams": {}
  }
}

list_log_streams is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Linode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_log_streams

What does the list_log_streams tool do? +

Get a list of all log streams. 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 list_log_streams? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for list_log_streams: 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 list_log_streams? +

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

Can I rate-limit list_log_streams? +

Yes. Add a rate_limit block to the list_log_streams 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 list_log_streams completely? +

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

list_log_streams 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.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.