list_plugins
List installed plugins and their enabled status.
This record as markdown: /tools/jjpxdev-unreal-mcp/list-plugins.md
What list_plugins does on Unreal
AI agents call list_plugins to retrieve information from Unreal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_plugins is rated Low
This tool retrieves and displays information about installed plugins and their enabled/disabled states. It performs no modifications, executions, or destructive operations. It is a straightforward read operation that queries system configuration data, making it a low-severity Read category tool.
From the tool's definition Tool name 'list_plugins' combined with description 'List installed plugins and their enabled status' indicates a purely informational query operation that retrieves data about plugin configuration without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs list_plugins safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every list_plugins call is checked against it from then on.
Questions about list_plugins
List installed plugins and their enabled status. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.
Register the Unreal 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 Unreal. Nothing to install.
list_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_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_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_plugins is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue