Lists all suspended subscriptions using Plesk internal CLI
AI agents call plesk_list_suspended_subscriptions to retrieve information from Plesk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about suspended subscriptions without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—an agent could misuse it only to gather information about suspended accounts, which is low-risk.
From the tool's definition Tool name contains 'list' and description states 'Lists all suspended subscriptions' — a retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Lists all suspended subscriptions using Plesk internal CLI. It is categorised as a Read tool in the Plesk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Plesk MCP Server MCP server in PolicyLayer and add a rule for plesk_list_suspended_subscriptions: 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 Plesk MCP Server. Nothing to install.
plesk_list_suspended_subscriptions 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 plesk_list_suspended_subscriptions 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 plesk_list_suspended_subscriptions. 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.
plesk_list_suspended_subscriptions is provided by the Plesk MCP Server MCP server (klan1/plesk-mcp). 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 →