Find load shedding areas near a GPS location. Useful when you know coordinates but not the area name.
AI agents call get_areas_nearby 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 retrieves and returns geolocation-based load shedding area data without modifying, deleting, or executing any operations. It is a straightforward read operation that queries the EskomSePush API for informational purposes only. The blast radius of misuse is minimal—an agent could only retrieve unwanted geographic data.
From the tool's definition Tool name 'get_areas_nearby' and description 'Find load shedding areas near a GPS location' indicate a simple lookup/query operation. No side effects, modification, deletion, execution, or financial impact.
Documented attack patterns abuse exactly the kind of access get_areas_nearby 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_areas_nearby:
{
"version": "1",
"default": "deny",
"tools": {
"get_areas_nearby": {}
}
}get_areas_nearby 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.
Find load shedding areas near a GPS location. Useful when you know coordinates but not the area name. 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_areas_nearby: 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_areas_nearby 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_areas_nearby 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_areas_nearby. 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_areas_nearby 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.