list_plugins

List installed YAML plugins from ~/.pentest-ai/plugins/.

SERVERPentest Ai SOURCE0xsteph/pentest-ai

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xsteph-pentest-ai/list-plugins.md

WHAT IT DOES

What list_plugins does on Pentest Ai

AI agents call list_plugins to retrieve information from Pentest Ai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_plugins is rated Low

This tool retrieves and displays information about installed plugins from a directory without creating, modifying, deleting, or executing anything. It is a simple informational query, fitting squarely within the Read category. Severity is low because the blast radius is confined to information disclosure of plugin metadata, which does not directly impact system security or functionality.

From the tool's definition Tool description explicitly states 'List installed YAML plugins' — a retrieval/query operation with no modification or execution. The action is read-only enumeration of local plugin configurations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_plugins safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_plugins, this is the rule to start with:

list_plugins Allowed

list_plugins is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_plugins": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentest Ai, apply this rule, and every list_plugins call is checked against it from then on.

FAQ

Questions about list_plugins

What does the list_plugins tool do? +

List installed YAML plugins from ~/.pentest-ai/plugins/. It is categorised as a Read tool in the Pentest Ai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_plugins? +

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

What risk level is list_plugins? +

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

Can I rate-limit list_plugins? +

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

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

list_plugins is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentest Ai, and thousands of servers like it.

This server

All 51 Pentest Ai tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →