AI agents invoke platform-load-balancer-restart to trigger actions in SettleMint. 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.
Restarting a load balancer is an operational action that triggers an external infrastructure operation, potentially causing downtime or disruption to services routing through it. This fits the Execute category as it triggers an external operation. However, the description is empty, which lowers confidence.
From the tool's definition Tool name 'platform-load-balancer-restart' implies restarting a load balancer component on the blockchain infrastructure platform.
Documented attack patterns abuse exactly the kind of access platform-load-balancer-restart gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SettleMint, and nothing reaches the server without passing your rules. This is the rule we recommend for platform-load-balancer-restart:
{
"version": "1",
"default": "deny",
"tools": {
"platform-load-balancer-restart": {
"limits": [
{
"counter": "platform-load-balancer-restart_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}platform-load-balancer-restart 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.
platform-load-balancer-restart. It is categorised as a Execute tool in the SettleMint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SettleMint MCP server in PolicyLayer and add a rule for platform-load-balancer-restart: 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 SettleMint. Nothing to install.
platform-load-balancer-restart 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 platform-load-balancer-restart 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 platform-load-balancer-restart. 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.
platform-load-balancer-restart is provided by the SettleMint MCP server (settlemint/sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SettleMint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 SettleMint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.