reload_runtime_config

THE RISK

High Risk

Why reload_runtime_config needs a policy

Reloading runtime configuration is an active execution operation that modifies the running state of the server by re-reading and applying config files. While it doesn't directly delete data or move money, it can have significant side effects (e.g., changing anti-bot bypass settings, proxy configurations, or scraping behaviors) that affect ongoing and future operations.

From the tool's definition 'Reload runtime settings from config files' — triggers an active reload operation that changes the server's live runtime configuration

Documented attack patterns abuse exactly the kind of access reload_runtime_config gives an agent:

POLICY

How to control reload_runtime_config

PolicyLayer is an MCP gateway — it sits between your AI agents and Web Scraper, and nothing reaches the server without passing your rules. This is the rule we recommend for reload_runtime_config:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reload_runtime_config": {
      "limits": [
        {
          "counter": "reload_runtime_config_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

reload_runtime_config stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Web Scraper — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Web Scraper tools

Destructive clear_cache Clear the response cache. Use when cached data may be stale. Destructive clear_history Clear scraping history. Destructive clear_host_profile Delete one host profile record from the profile store. Destructive clear_session Clear a browser session (cookies, storage). Use for fresh starts. Execute cancel_job Cancel a running async job. Execute browser_evaluate Run a JavaScript expression on the current page and return the result. Execute browser_navigate Navigate the interactive browser to a URL. Execute browser_solve_challenge Explicitly trigger challenge detection and solving on the current page.

All 62 Web Scraper tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Web Scraper → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reload_runtime_config

What does the reload_runtime_config tool do? +

Reload runtime settings from config files. It is categorised as a Execute tool in the Web Scraper MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reload_runtime_config? +

Register the Web Scraper MCP server in PolicyLayer and add a rule for reload_runtime_config: 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 Web Scraper. Nothing to install.

What risk level is reload_runtime_config? +

reload_runtime_config is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reload_runtime_config? +

Yes. Add a rate_limit block to the reload_runtime_config 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 reload_runtime_config completely? +

Set action: deny in the PolicyLayer policy for reload_runtime_config. 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 reload_runtime_config? +

reload_runtime_config is provided by the Web Scraper MCP server (imyourboyroy/webscrapertoolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Web Scraper tool call.

Start from Web Scraper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →