Return the curated allow-list of Volatility 3 plugins exposed by this
AI agents call list_available_plugins to retrieve information from Protocol-SIFT-Async-Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries a static list of allowed plugins. It has no side effects, does not execute code, does not modify data, and does not perform destructive actions. The 'allow-list' nature indicates a read-only, informational response.
From the tool's definition Tool name is 'list_available_plugins' and description states 'Return the curated allow-list of Volatility 3 plugins exposed by this' — a straightforward enumeration/retrieval operation with no modification, deletion, or execution of external processes.
Attacks that exploit this kind of access
Return the curated allow-list of Volatility 3 plugins exposed by this. It is categorised as a Read tool in the Protocol-SIFT-Async-Bridge MCP Server, which means it retrieves data without modifying state.
Register the Protocol-SIFT-Async-Bridge MCP server in PolicyLayer and add a rule for list_available_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 Protocol-SIFT-Async-Bridge. Nothing to install.
list_available_plugins is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_available_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.
Set action: deny in the PolicyLayer policy for list_available_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.
list_available_plugins is provided by the Protocol-SIFT-Async-Bridge MCP server (mwarsss/protocol-sift-async-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →