get_service_metrics

Get metrics for entities of a specific monitoring service type

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-service-metrics.md

WHAT IT DOES

What get_service_metrics does on Linode MCP Server

AI agents call get_service_metrics 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_service_metrics is rated Low

This tool retrieves monitoring metrics/data from Linode services. It is a read-only operation that queries existing metrics without creating, modifying, executing code, deleting data, or making financial changes. The blast radius of misuse is minimal—an agent could only access metrics data that would be accessible through normal monitoring queries.

From the tool's definition Tool name 'get_service_metrics' and description 'Get metrics for entities of a specific monitoring service type' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_service_metrics 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_service_metrics, this is the rule to start with:

get_service_metrics Allowed

get_service_metrics 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_service_metrics": {}
  }
}

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_service_metrics call is checked against it from then on.

FAQ

Questions about get_service_metrics

What does the get_service_metrics tool do? +

Get metrics for entities of a specific monitoring service type. 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_service_metrics? +

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

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

Can I rate-limit get_service_metrics? +

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

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

get_service_metrics 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 →