// SCAN REPORT

Gst

17 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

2 can modify or destroy data

15 read-only

17 tools total

Community server · catalogue entry verified 02/07/2026

How to control Gst ↓

TOOL MAP

What Gst exposes to your agents

Read (15) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Gst tools

Execute · High run_pipeline This tool executes external operations (GStreamer pipelines) whose effects depend entirely on the pipeline arguments provided. Execute · High stop_pipeline This tool executes a command to stop a running GStreamer pipeline, which is an external operation that modifies the runtime state of a system process.

2 of Gst's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Gst

PolicyLayer is an MCP gateway — it sits between your AI agents and Gst, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "check_caps_compatible": {
    "limits": [
      {
        "counter": "check_caps_compatible_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Gst — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GST →

Instant setup, no code required.

FULL CATALOGUE

All 17 Gst tools

EXECUTE 2 tools

Execute run_pipeline Run a GStreamer pipeline. Can run synchronously with timeout or asynchronously. CRITICAL: Do NOT call this too Execute stop_pipeline Stop a running GStreamer pipeline

READ 15 tools

Read check_caps_compatible Check if two GStreamer caps can intersect (are compatible) Read check_elements_can_link Check if two GStreamer elements can link based on their pad caps Read fetch_online_docs Fetch documentation from GStreamer website for an element Read get_element_info Get detailed information about a GStreamer element including properties, pads, caps templates, and signals Read get_examples Get GStreamer pipeline examples by category (playback, transcoding, streaming, capture, effects, testing, anal Read get_pipeline_graph Generate a DOT graph representation of a GStreamer pipeline Read get_pipeline_status Get the status of a running GStreamer pipeline Read get_plugin_info Get detailed information about a GStreamer plugin including its elements Read list_elements List available GStreamer elements, optionally filtered by category (source, sink, decoder, encoder, muxer, dem Read list_plugins List all installed GStreamer plugins with version and description Read list_running_pipelines List all currently running GStreamer pipelines Read parse_caps Parse a GStreamer caps string and return structured information Read search_elements Search for GStreamer elements by name, description, or caps Read suggest_converter Suggest converter elements to link incompatible GStreamer elements Read validate_pipeline Validate a GStreamer pipeline string without running it. Reports errors and suggestions. IMPORTANT: Always use

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Gst

Is the Gst MCP server safe to use without restrictions? +

The Gst server is primarily read-only with 15 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Gst MCP server expose? +

17 tools across 2 categories: Execute, Read. 15 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Gst? +

Register the Gst MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Gst tool call.

Deterministic rules across all 17 Gst tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GST →

Instant setup, no code required.

17 Gst tools catalogued and risk-classified — across an index of 43,000+ MCP servers.