Low Risk

get_longview_plan

Get the current Longview plan

How to control get_longview_plan ↓

What get_longview_plan does on Linode MCP Server

AI agents call get_longview_plan 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 get_longview_plan needs a policy

This tool performs a read-only query of Linode's Longview monitoring plan status. It retrieves information about the current plan but does not create, modify, delete, or execute any changes to infrastructure or configurations. The blast radius of misuse is minimal — an attacker could only learn about the user's monitoring setup, not alter it.

From the tool's definition Tool name is 'get_longview_plan' and description states 'Get the current Longview plan' — a retrieval operation that queries existing monitoring/plan configuration without modifying, deleting, or executing operations.

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

How to control get_longview_plan

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 get_longview_plan:

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

get_longview_plan 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 get_longview_plan

What does the get_longview_plan tool do? +

Get the current Longview plan. 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_longview_plan? +

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

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

Can I rate-limit get_longview_plan? +

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

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

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