list_service_metric_definitions
List metric definitions for a specific monitoring service type
This record as markdown: /tools/takashito-linode-mcp-server/list-service-metric-definitions.md
What list_service_metric_definitions does on Linode MCP Server
AI agents call list_service_metric_definitions 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.
Why list_service_metric_definitions is rated Low
This tool retrieves and lists metric definitions—informational data about available monitoring metrics. It performs no state changes, does not execute operations, and does not access sensitive operational data beyond schema/metadata. The 'list' verb and 'definitions' object confirm this is a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_service_metric_definitions' and description 'List metric definitions for a specific monitoring service type' indicate a retrieval operation that queries monitoring metadata without modifying or executing actions.
Attacks that exploit this kind of access
The rule that runs list_service_metric_definitions 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 list_service_metric_definitions, this is the rule to start with:
list_service_metric_definitions 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 Linode MCP Server, apply this rule, and every list_service_metric_definitions call is checked against it from then on.
Questions about list_service_metric_definitions
List metric definitions for 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.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for list_service_metric_definitions: 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.
list_service_metric_definitions 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 list_service_metric_definitions 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 list_service_metric_definitions. 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.
list_service_metric_definitions 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.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue