Check how many EskomSePush API calls you have remaining today. Free tier allows 50 calls per day.
AI agents call check_allowance 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 current API allowance information. It performs no data creation, modification, deletion, or external execution. The action is a straightforward lookup of quota status, consistent with the Read category for retrieval operations without side effects. Severity is low because misuse poses minimal risk—checking allowance cannot degrade system functionality or cause harm.
From the tool's definition Tool description states it 'Check[s] how many EskomSePush API calls you have remaining today' — a pure query operation that retrieves usage/quota data with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access check_allowance 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 check_allowance:
{
"version": "1",
"default": "deny",
"tools": {
"check_allowance": {}
}
}check_allowance 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.
Check how many EskomSePush API calls you have remaining today. Free tier allows 50 calls per day. 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 check_allowance: 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.
check_allowance 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 check_allowance 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 check_allowance. 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.
check_allowance 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.