AI agents invoke mcp_reload to trigger actions in 1MCP Server. 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.
Reloading an MCP server or configuration is an operational trigger that restarts or reinitializes a live service. This is an Execute-category action because it causes an external system operation whose effects depend on the current state and configuration. It could disrupt active connections, apply new (potentially malicious) configurations, or alter the behavior of all aggregated MCP servers.
From the tool's definition "Reload MCP server or configuration" — triggers a reload/restart operation on a running MCP server or its configuration
Documented attack patterns abuse exactly the kind of access mcp_reload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_reload:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_reload": {
"limits": [
{
"counter": "mcp_reload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mcp_reload 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.
Free to start. No card required.
Reload MCP server or configuration. It is categorised as a Execute tool in the 1MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1MCP Server MCP server in PolicyLayer and add a rule for mcp_reload: 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 1MCP Server. Nothing to install.
mcp_reload 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 mcp_reload 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 mcp_reload. 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.
mcp_reload is provided by the 1MCP Server MCP server (1mcp-app/agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 1MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 1MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.