Reload servers from the registry and rebuild the in-memory registry.
AI agents invoke reload_servers to trigger actions in SuperMCP 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.
This tool performs an active system operation: reloading configuration from a persistent store and reconstructing the in-memory registry. It is not a simple read (it modifies runtime state) nor a write (it doesn't persist new data), but rather executes an administrative action that reinitializes the orchestration layer.
From the tool's definition 'Reload servers from the registry and rebuild the in-memory registry' — triggers a rebuild/reinitialization operation on the in-memory server registry
Attacks that exploit this kind of access
Reload servers from the registry and rebuild the in-memory registry. It is categorised as a Execute tool in the SuperMCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SuperMCP Server MCP server in PolicyLayer and add a rule for reload_servers: 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 SuperMCP Server. Nothing to install.
reload_servers 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 reload_servers 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 reload_servers. 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.
reload_servers is provided by the SuperMCP Server MCP server (yakupatahanov/supermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →