Return the --help output for a specific Volatility 3 plugin.
AI agents call get_plugin_help 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 queries and displays informational content about available plugins without executing any forensic analysis, modifying evidence, or triggering external operations. It is purely a documentation lookup facility, making it a Read category tool with low severity since misuse would only expose plugin documentation already available to authorized users of the forensics server.
From the tool's definition Tool retrieves and returns help documentation (--help output) for a Volatility 3 plugin. The description explicitly states it 'returns' help text with no modification, creation, deletion, or execution of forensic operations.
Attacks that exploit this kind of access
Return the --help output for a specific Volatility 3 plugin. 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 get_plugin_help: 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.
get_plugin_help 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 get_plugin_help 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 get_plugin_help. 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.
get_plugin_help 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 →