AI agents invoke gandi_simplehosting_perform_instance_action to trigger actions in Gandi. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name 'perform_instance_action' strongly implies execution of operational actions on a SimpleHosting instance (e.g., restart, start, stop, deploy). Since the description is empty, exact capabilities are unknown, but 'perform action' language indicates execution of external operations. Given the server context (production-grade hosting management), misuse could impact live services.
From the tool's definition Tool name contains 'perform_instance_action' suggesting it triggers operations on a hosting instance; description is empty and uninformative.
Attacks that exploit this kind of access
gandi_simplehosting_perform_instance_action. It is categorised as a Execute tool in the Gandi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_simplehosting_perform_instance_action: 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 Gandi. Nothing to install.
gandi_simplehosting_perform_instance_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gandi_simplehosting_perform_instance_action 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 gandi_simplehosting_perform_instance_action. 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.
gandi_simplehosting_perform_instance_action is provided by the Gandi MCP server (millsymills-com/gandi-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 →