This record as markdown: /tools/io-github-dave-london-go/reload.md
What reload does on Go
AI agents invoke reload to trigger actions in Go. 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.
Why reload is rated High
The tool rebuilds a server or project, which constitutes executing a build process. Rebuilding the MCP server itself is particularly impactful as it can affect the running environment. The description appears truncated, lowering confidence slightly, but 'Rebuilds' clearly implies an Execute-category action with potentially high blast radius if misused on the MCP server itself.
From the tool's definition 'Rebuilds the MCP server (or a specified project) and sends a' — triggers a rebuild/execution of a server or project
Attacks that exploit this kind of access
The rule that runs reload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reload, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Go, apply this rule, and every reload call is checked against it from then on.
Questions about reload
Rebuilds the MCP server (or a specified project) and sends a. It is categorised as a Execute tool in the Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Go MCP server in PolicyLayer and add a rule for 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 Go. Nothing to install.
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 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 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.
reload is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue