Check the status and generation progress of a site. Returns detailed progress information including: - stage: Current step (initialization, validation, research, strategy, generation, assembly, completion) - overallProgress: Total progress 0-100 across all stages (use this for progress bars) - st...
Risk signalsBulk/mass operation — affects multiple targets
Part of the WebZum - The Hosting Layer for AI-Generated Web Content server.
Free to start. No card required.
AI agents call get_site_status to retrieve information from WebZum - The Hosting Layer for AI-Generated Web Content without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_site_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_site_status": {}
}
}See the full WebZum - The Hosting Layer for AI-Generated Web Content policy for all 16 tools.
These attack patterns abuse exactly the kind of access get_site_status gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check the status and generation progress of a site. Returns detailed progress information including: - stage: Current step (initialization, validation, research, strategy, generation, assembly, completion) - overallProgress: Total progress 0-100 across all stages (use this for progress bars) - stageProgress: Progress within current stage 0-100 - message: Human-readable status message - isComplete: Boolean - stop polling when true Use the versionId returned from create_site for real-time progress polling. Poll every 5-10 seconds while isComplete is false.. It is categorised as a Read tool in the WebZum - The Hosting Layer for AI-Generated Web Content MCP Server, which means it retrieves data without modifying state.
Register the WebZum - The Hosting Layer for AI-Generated Web Content MCP server in PolicyLayer and add a rule for get_site_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 WebZum - The Hosting Layer for AI-Generated Web Content. Nothing to install.
get_site_status 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 get_site_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 get_site_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.
get_site_status is provided by the WebZum - The Hosting Layer for AI-Generated Web Content MCP server (https://webzum.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 WebZum - The Hosting Layer for AI-Generated Web Content tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.