Low Risk

tailpipe_plugin_list

List all installed Tailpipe plugins with their versions and associated partitions.

How to control tailpipe_plugin_list ↓

What tailpipe_plugin_list does on Tailpipe

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

Low Risk

Why tailpipe_plugin_list needs a policy

This tool retrieves and displays plugin information (list, versions, partition associations) with no side effects, modification, or execution capability. It is purely informational, making it a Read category tool with low severity since disclosing plugin metadata poses minimal security risk unless sensitive plugin names or versions could enable targeted attacks.

From the tool's definition Tool name 'tailpipe_plugin_list' with description 'List all installed Tailpipe plugins with their versions and associated partitions' indicates retrieval of metadata about installed plugins without modification or execution.

Documented attack patterns abuse exactly the kind of access tailpipe_plugin_list gives an agent:

How to control tailpipe_plugin_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Tailpipe, and nothing reaches the server without passing your rules. This is the rule we recommend for tailpipe_plugin_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tailpipe_plugin_list": {}
  }
}

tailpipe_plugin_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tailpipe — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about tailpipe_plugin_list

What does the tailpipe_plugin_list tool do? +

List all installed Tailpipe plugins with their versions and associated partitions. It is categorised as a Read tool in the Tailpipe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tailpipe_plugin_list? +

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

What risk level is tailpipe_plugin_list? +

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

Can I rate-limit tailpipe_plugin_list? +

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

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

tailpipe_plugin_list is provided by the Tailpipe MCP server (turbot/tailpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tailpipe tool call.

Start from Tailpipe, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.