list_timeseries
Lists time series data from the Google Cloud Monitoring API
This record as markdown: /tools/com-googleapis-monitoring-mcp/list-timeseries.md
What list_timeseries does on Mcp
AI agents call list_timeseries to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Required. The [project](https://cloud.google.com/monitoring/api/v3#project_name), organization or folder on which to execute the request. The format is: project |
view | string | Yes | Required. Specifies which information is returned about the time series. |
filter | string | Yes | Required. A [monitoring filter](https://cloud.google.com/monitoring/api/v3/filters) that specifies which time series should be returned. The filter must specify |
orderBy | string | — | Unsupported: must be left blank. The points in each time series are currently returned in reverse time order (most recent to oldest). |
interval | object | Yes | Required. The time interval for which results should be returned. Only time series that contain data points in the specified interval are included in the respon |
pageSize | integer | — | A positive number that is the maximum number of results to return. If `page_size` is empty or more than 100,000 results, the effective `page_size` is 100,000 re |
pageToken | string | — | If this field is not empty then it must contain the `nextPageToken` value returned by a previous call to this method. Using this field causes the method to retu |
aggregation | object | — | Specifies the alignment of data points in individual time series as well as how to combine the retrieved time series across specified labels. By default (if no |
secondaryAggregation | object | — | Apply a second aggregation after `aggregation` is applied. May only be specified if `aggregation` is specified. |
Parameters from the server's own tool schema.
Why list_timeseries is rated Low
This tool queries and retrieves time series metrics data without creating, modifying, deleting, or executing operations. It is purely informational and has no side effects on infrastructure or data integrity. The blast radius of misuse is limited to unauthorized visibility into monitoring data.
From the tool's definition Tool name 'list_timeseries' and description 'Lists time series data from the Google Cloud Monitoring API' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs list_timeseries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_timeseries, this is the rule to start with:
list_timeseries 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 Mcp, apply this rule, and every list_timeseries call is checked against it from then on.
Questions about list_timeseries
Lists time series data from the Google Cloud Monitoring API. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_timeseries accepts 9 parameters: name, view, filter, orderBy, interval, pageSize, pageToken, aggregation, secondaryAggregation. Required: name, view, filter, interval. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for list_timeseries: 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 Mcp. Nothing to install.
list_timeseries 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_timeseries 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_timeseries. 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_timeseries is provided by the MCP server (https://monitoring.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue