Get the current national load shedding stage for both Eskom and Cape Town. Use this to find out what stage we are on right now.
AI agents call get_status to retrieve information from Eskomsepush without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns real-time status information about South African load shedding stages. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. The blast radius of misuse is minimal—an agent could only obtain current public utility status information.
From the tool's definition Tool retrieves current load shedding stage data with no modification capability: 'Get the current national load shedding stage' and 'find out what stage we are on right now' describe a pure query/fetch operation.
Documented attack patterns abuse exactly the kind of access get_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Eskomsepush, and nothing reaches the server without passing your rules. This is the rule we recommend for get_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_status": {}
}
}get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current national load shedding stage for both Eskom and Cape Town. Use this to find out what stage we are on right now. It is categorised as a Read tool in the Eskomsepush MCP Server, which means it retrieves data without modifying state.
Register the Eskomsepush MCP server in PolicyLayer and add a rule for get_status: 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 Eskomsepush. Nothing to install.
get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_status 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 get_status. 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.
get_status is provided by the Eskomsepush MCP server (zukhanyendiki9-code/eskomsepush-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Eskomsepush, 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.
5 Eskomsepush tools catalogued and risk-classified — across an index of 43,000+ MCP servers.