Get the upcoming load shedding schedule and events for a specific area. Requires an area ID — use search_areas first if you don
AI agents call get_area_schedule 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 reads and returns scheduling data for a specific area without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an attacker could only retrieve public load shedding information already available through normal API access.
From the tool's definition Tool retrieves 'upcoming load shedding schedule and events' with no modification or deletion capabilities. Description indicates a query operation that returns data about scheduled events.
Documented attack patterns abuse exactly the kind of access get_area_schedule 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_area_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"get_area_schedule": {}
}
}get_area_schedule 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 upcoming load shedding schedule and events for a specific area. Requires an area ID — use search_areas first if you don. 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_area_schedule: 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_area_schedule 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_area_schedule 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_area_schedule. 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_area_schedule 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.