list_connection_profiles
Lists connection profiles in a given project and location. For example: { parent: "projects/my-project/locations/us-central1" create_time_after: 2025-10-02T10:15:33Z create_time_before: 2025-10-03T00:00:00Z display_name: bookstore page_size: 100 } will return up to 100 connection profiles in proj...
This record as markdown: /tools/com-googleapis-datastream-mcp/list-connection-profiles.md
What list_connection_profiles does on Mcp
AI agents call list_connection_profiles 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 |
|---|---|---|---|
parent | string | Yes | Required. The parent that owns the collection of connection profiles. Must be in the format `projects/*/locations/*`. For example: 'projects/my-project/location |
pageSize | integer | — | Optional. Use to limit the number of connection profiles returned. Valid values are between 1 and 1000 inclusive. Defaults to 1000 if not provided or outside of |
pageToken | string | — | Optional. A page token, received from a previous `list_connection_profiles` call. Provide this to retrieve the subsequent page. When paginating, all other param |
displayName | string | — | Optional. Use to get connection profiles whose display name contains the provided name. |
createTimeAfter | string | — | Optional. Use to get connection profiles that were created on or after the provided date/time, formatted as RFC-3339. Common Examples: 2023-09-24T15:30:00Z or 2 |
createTimeBefore | string | — | Optional. Use to get connection profiles that were created before the provided date/time, formatted as RFC-3339. Common Examples: 2023-09-24T15:30:00Z or 2023-0 |
Parameters from the server's own tool schema.
Why list_connection_profiles is rated Low
This tool retrieves and queries existing connection profile metadata without side effects. It returns filtered results but does not create, modify, delete, or execute any operations. It is a straightforward Read operation with minimal blast radius if misused by an AI agent—worst case being disclosure of connection profile metadata within the caller's Google Cloud project.
From the tool's definition Tool name is 'list_connection_profiles' and description states it 'Lists connection profiles in a given project and location.' The example shows filtering and pagination parameters (parent, create_time_after, create_time_before, display_name, page_size) with…
Attacks that exploit this kind of access
The rule that runs list_connection_profiles 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_connection_profiles, this is the rule to start with:
list_connection_profiles 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_connection_profiles call is checked against it from then on.
Questions about list_connection_profiles
Lists connection profiles in a given project and location. For example: { parent: "projects/my-project/locations/us-central1" create_time_after: 2025-10-02T10:15:33Z create_time_before: 2025-10-03T00:00:00Z display_name: bookstore page_size: 100 } will return up to 100 connection profiles in projects/my-project/locations/us-central1 that were created on or after 2025-10-02T10:15:33 UTC and before 2025-10-03T00:00:00 UTC, and have "bookstore" in their display name. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_connection_profiles accepts 6 parameters: parent, pageSize, pageToken, displayName, createTimeAfter, createTimeBefore. Required: parent. 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_connection_profiles: 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_connection_profiles 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_connection_profiles 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_connection_profiles. 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_connection_profiles is provided by the MCP server (https://datastream.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