lookup_stream_object
Lookup a stream object by its source object identifier. Parameters: * The 'parent' parameter is the name of the stream in the form: 'projects/{project name}/locations/{location}/streams/{stream name}', for example: 'projects/my-project/locations/us-central1/streams/my-stream'. * The 'source_objec...
This record as markdown: /tools/com-googleapis-datastream-mcp/lookup-stream-object.md
What lookup_stream_object does on Mcp
AI agents call lookup_stream_object 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 stream that owns the collection of objects. |
sourceObjectIdentifier | object | Yes | Required. The source object identifier which maps to the stream object. |
Parameters from the server's own tool schema.
Why lookup_stream_object is rated Low
This tool performs a read-only lookup of stream object metadata within Google Cloud Datastream. It takes a stream identifier and source object identifier as parameters and returns information about that object. There are no side effects, no data modification, no code execution, and no destructive operations. This is clearly a Read category tool with low severity since it only retrieves information.
From the tool's definition Tool name is 'lookup_stream_object' and description states it 'Lookup a stream object by its source object identifier' — a query operation that retrieves metadata about a stream object without modifying, deleting, or executing code.
Attacks that exploit this kind of access
The rule that runs lookup_stream_object 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 lookup_stream_object, this is the rule to start with:
lookup_stream_object 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 lookup_stream_object call is checked against it from then on.
Questions about lookup_stream_object
Lookup a stream object by its source object identifier. Parameters: * The 'parent' parameter is the name of the stream in the form: 'projects/{project name}/locations/{location}/streams/{stream name}', for example: 'projects/my-project/locations/us-central1/streams/my-stream'. * The 'source_object_identifier' parameter is the source database object identifier. Different source databases have different identifier formats. Examples: * Oracle, PostgreSQL, SQL Server and Spanner databases the identifier is 'schema' and 'table'. * MySQL databases the identifier is 'database' and 'table'. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
lookup_stream_object accepts 2 parameters: parent, sourceObjectIdentifier. Required: parent, sourceObjectIdentifier. 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 lookup_stream_object: 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.
lookup_stream_object 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 lookup_stream_object 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 lookup_stream_object. 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.
lookup_stream_object 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