# list_timeseries

Lists time series data from the Google Cloud Monitoring API

Agent View of the PolicyLayer registry record for `list_timeseries`. HTML page: https://policylayer.com/tools/com-googleapis-monitoring-mcp/list-timeseries

## Facts

- Tool: `list_timeseries`
- Server: Mcp (`https://monitoring.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-monitoring-mcp.md
- Homepage: https://github.com/https://monitoring.googleapis.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 9 (4 required)
- Recommended policy verdict: Allowed

## Parameters

| 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 | no | 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 | no | 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 | no | 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 | no | 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 | no | Apply a second aggregation after `aggregation` is applied. May only be specified if `aggregation` is specified. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_timeseries",
    "arguments": {
      "name": "<name>",
      "view": "<view>",
      "filter": "<filter>",
      "interval": {}
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_timeseries": {}
  }
}
```

## Other tools on Mcp (8)

- `get_alert` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/get-alert.md
- `get_alert_policy` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/get-alert-policy.md
- `get_dashboard` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/get-dashboard.md
- `list_alert_policies` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/list-alert-policies.md
- `list_alerts` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/list-alerts.md
- `list_dashboards` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/list-dashboards.md
- `list_metric_descriptors` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/list-metric-descriptors.md
- `query_range` — Read — https://policylayer.com/tools/com-googleapis-monitoring-mcp/query-range.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-monitoring-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-monitoring-mcp