list_running_pipelines

List all currently running GStreamer pipelines

Server Gst wizenink/gst-mcp
Category Read
Risk class Low
Parameters 00 required

What list_running_pipelines does on Gst

AI agents call list_running_pipelines to retrieve information from Gst without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_running_pipelines needs a policy

This tool only queries and returns information about existing pipeline states. It performs no side effects—no pipelines are created, modified, deleted, or executed. It is a straightforward informational read operation, appropriate for an introspection and development utility.

From the tool's definition Tool name 'list_running_pipelines' and description 'List all currently running GStreamer pipelines' indicate retrieval of status information with no modification, creation, deletion, or execution of pipelines.

Questions about list_running_pipelines

What does the list_running_pipelines tool do? +

List all currently running GStreamer pipelines. It is categorised as a Read tool in the Gst MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_running_pipelines? +

Register the Gst MCP server in PolicyLayer and add a rule for list_running_pipelines: 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 Gst. Nothing to install.

What risk level is list_running_pipelines? +

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

Can I rate-limit list_running_pipelines? +

Yes. Add a rate_limit block to the list_running_pipelines 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 list_running_pipelines completely? +

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

list_running_pipelines is provided by the Gst MCP server (wizenink/gst-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.