get_instance_stats_by_date
Get statistics for a Linode instance for a specific month
This record as markdown: /tools/takashito-linode-mcp-server/get-instance-stats-by-date.md
What get_instance_stats_by_date does on Linode MCP Server
AI agents call get_instance_stats_by_date 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 get_instance_stats_by_date is rated Low
This tool retrieves historical statistics and monitoring data for a Linode instance. It performs a read-only query operation that retrieves pre-computed metrics for a specified time period. No resources are created, modified, deleted, or executed.
From the tool's definition Tool name 'get_instance_stats_by_date' and description 'Get statistics for a Linode instance for a specific month' indicate a query/retrieval operation with no side effects. Returns monitoring data without modifying infrastructure.
Attacks that exploit this kind of access
The rule that runs get_instance_stats_by_date 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_instance_stats_by_date, this is the rule to start with:
get_instance_stats_by_date 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 get_instance_stats_by_date call is checked against it from then on.
Questions about get_instance_stats_by_date
Get statistics for a Linode instance for a specific month. 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 get_instance_stats_by_date: 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.
get_instance_stats_by_date 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 get_instance_stats_by_date 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 get_instance_stats_by_date. 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.
get_instance_stats_by_date 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