This record as markdown: /tools/aapanel-mcp/plugin-set-status.md
What plugin_set_status does on Aapanel
AI agents use plugin_set_status to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why plugin_set_status is rated Medium
Enabling or disabling a plugin is a write operation that changes system configuration. While reversible, it can have significant side effects on server functionality—disabling a critical plugin could break services, and enabling a malicious plugin could compromise the system. The impact depends on which plugin is targeted, justifying 'high' severity.
From the tool's definition Tool description states 'Enable or disable a plugin.' This modifies the state of a plugin, which is a reversible configuration change.
Attacks that exploit this kind of access
The rule that runs plugin_set_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For plugin_set_status, this is the rule to start with:
plugin_set_status 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 Aapanel, apply this rule, and every plugin_set_status call is checked against it from then on.
Questions about plugin_set_status
Enable or disable a plugin. It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for plugin_set_status: 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 Aapanel. Nothing to install.
plugin_set_status 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 plugin_set_status 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 plugin_set_status. 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.
plugin_set_status is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue