agency_import_archive
Import an Agency Plan website from an archive.
This record as markdown: /tools/hostinger-mcp/agency-import-archive.md
What agency_import_archive does on Hostinger
AI agents use agency_import_archive to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why agency_import_archive is rated Medium
The tool creates or restores a website from an archive, which is a reversible modification operation. While it affects hosted infrastructure, it does not permanently delete data (thus not Destructive), execute arbitrary code (thus not Execute), or move money (thus not Financial).
From the tool's definition Tool name 'agency_import_archive' and description 'Import an Agency Plan website from an archive' indicate creation/restoration of website data from an archive file. This is a write operation that modifies the hosted environment.
Attacks that exploit this kind of access
The rule that runs agency_import_archive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agency_import_archive, this is the rule to start with:
agency_import_archive 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 Hostinger, apply this rule, and every agency_import_archive call is checked against it from then on.
Questions about agency_import_archive
Import an Agency Plan website from an archive. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for agency_import_archive: 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 Hostinger. Nothing to install.
agency_import_archive 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 agency_import_archive 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 agency_import_archive. 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.
agency_import_archive is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue