New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

plugin_set_status

Enable or disable a plugin.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about plugin_set_status

What does the plugin_set_status tool do? +

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.

How do I enforce a policy on plugin_set_status? +

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.

What risk level is plugin_set_status? +

plugin_set_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit plugin_set_status? +

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.

How do I block plugin_set_status completely? +

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.

What MCP server provides plugin_set_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aapanel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.