Low Risk

reload_config

Reload configuration from disk. Use after editing mcacp.json to pick up new agent_servers entries or changed settings. Returns the new config.

Part of the Mcacp server.

reload_config is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCACP →

Free to start. No card required.

AI agents call reload_config to retrieve information from Mcacp 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 reload_config 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reload_config": {}
  }
}

See the full Mcacp policy for all 24 tools.

Get this rule live on your own Mcacp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCACP →

View all 24 tools →

These attack patterns abuse exactly the kind of access reload_config gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so reload_config only ever does what you allow.

SECURE MCACP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the reload_config tool do? +

Reload configuration from disk. Use after editing mcacp.json to pick up new agent_servers entries or changed settings. Returns the new config.. It is categorised as a Read tool in the Mcacp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reload_config? +

Register the Mcacp MCP server in PolicyLayer and add a rule for reload_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 Mcacp. Nothing to install.

What risk level is reload_config? +

reload_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit reload_config? +

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

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

reload_config is provided by the Mcacp MCP server (mcacp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcacp tool call.

Deterministic rules across all 24 Mcacp 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.