get_plugin_info

Get detailed information about a GStreamer plugin including its elements

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

What get_plugin_info does on Gst

AI agents call get_plugin_info 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 get_plugin_info needs a policy

This is a pure read operation that queries and returns information about GStreamer plugins. There are no side effects, no data modification, no code execution, and no destructive actions. It fits the 'Read' category of tools that retrieve or query data. Severity is low because misuse poses minimal risk—returning plugin metadata cannot damage systems or data.

From the tool's definition Tool name is 'get_plugin_info' with description 'Get detailed information about a GStreamer plugin including its elements'.

Questions about get_plugin_info

What does the get_plugin_info tool do? +

Get detailed information about a GStreamer plugin including its elements. 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 get_plugin_info? +

Register the Gst MCP server in PolicyLayer and add a rule for get_plugin_info: 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 get_plugin_info? +

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

Can I rate-limit get_plugin_info? +

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

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

get_plugin_info 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.