Search for load shedding areas by name or suburb. Returns area IDs you can use with get_area_schedule. Always search first if you don
AI agents call search_areas 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 queries an external load shedding database to find area identifiers based on search criteria (name or suburb). It retrieves and returns information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could enumerate area data or perform reconnaissance, but cannot cause financial harm, destructive changes, or execute arbitrary code.
From the tool's definition Tool description: "Search for load shedding areas by name or suburb. Returns area IDs you can use with get_area_schedule." The verb "search" and the fact it "returns" data with no mention of modification indicates read-only retrieval.
Documented attack patterns abuse exactly the kind of access search_areas 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 search_areas:
{
"version": "1",
"default": "deny",
"tools": {
"search_areas": {}
}
}search_areas 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.
Search for load shedding areas by name or suburb. Returns area IDs you can use with get_area_schedule. Always search 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 search_areas: 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.
search_areas 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 search_areas 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 search_areas. 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.
search_areas 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.