New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_operation

Gets the status of a long-running operation. *Usage* Some tools (for example, run_stream) return a long-running operation. You can use this tool to get the status of the operation. It can be called repeatedly until the operation is complete. Parameters * name: The name of the operation to get. * ...

SERVERMcp SOURCEhttps://datastream.googleapis.com/mcp
Low RISK CLASS
Category Read
Parameters 10 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-datastream-mcp/get-operation.md

What get_operation does on Mcp

AI agents call get_operation 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.

ParameterTypeRequiredDescription
name string The name of the operation resource.

Parameters from the server's own tool schema.

Why get_operation is rated Low

This is a read-only operation that queries the status of existing operations. It has no side effects, cannot modify or delete data, and poses minimal risk even if called maliciously. An AI agent misusing this tool could only observe operation statuses, not affect any resources or data.

From the tool's definition Tool retrieves the status of a long-running operation without modifying any data. Description states 'Gets the status' and 'can be called repeatedly until the operation is complete', indicating purely informational retrieval.

Risk signalsBulk/mass operation — affects multiple targets

Questions about get_operation

What does the get_operation tool do? +

Gets the status of a long-running operation. *Usage* Some tools (for example, run_stream) return a long-running operation. You can use this tool to get the status of the operation. It can be called repeatedly until the operation is complete. Parameters * name: The name of the operation to get. * name should be the name returned by the tool that initiated the operation. * name should be in the format of: projects/{project}/locations/{location}/operations/{operation}. Returns * An Operation object that contains the status of the operation. * If the operation is not complete, the response will be empty. Do not check more than every ten seconds. * If the operation is complete, the response will contain either: * A response field that contains the result of the operation and indicates that it was successful. * A error field that indicates any errors that occurred during the operation. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_operation accept? +

get_operation accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_operation? +

Register the MCP server in PolicyLayer and add a rule for get_operation: 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.

What risk level is get_operation? +

get_operation is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_operation? +

Yes. Add a rate_limit block to the get_operation 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.

How do I block get_operation completely? +

Set action: deny in the PolicyLayer policy for get_operation. 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.

What MCP server provides get_operation? +

get_operation 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.