disable_plugin
Disable a plugin in the .uproject file. Requires editor restart to take effect.
This record as markdown: /tools/jjpxdev-unreal-mcp/disable-plugin.md
What disable_plugin does on Unreal
AI agents use disable_plugin to create or update resources in Unreal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
plugin_name | string | Yes | Plugin name to disable |
Parameters from the server's own tool schema.
Why disable_plugin is rated Medium
This tool modifies the .uproject project configuration file by disabling plugins, which affects the Unreal Engine project state. While reversible (the plugin can be re-enabled), it alters critical project configuration that controls which functionality is available. The impact is high because disabling plugins could break project functionality or dependencies, but not irreversible like deletion.
From the tool's definition Tool description states "Disable a plugin in the .uproject file" — modifies project configuration file. Changes are reversible (plugin can be re-enabled), distinguishing from destructive operations.
Attacks that exploit this kind of access
The rule that runs disable_plugin 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 disable_plugin, this is the rule to start with:
disable_plugin stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 disable_plugin call is checked against it from then on.
Questions about disable_plugin
Disable a plugin in the .uproject file. Requires editor restart to take effect. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
disable_plugin accepts 1 parameter: plugin_name. Required: plugin_name. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for disable_plugin: 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.
disable_plugin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disable_plugin 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 disable_plugin. 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.
disable_plugin 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