Monthly Islamic prayer-times calendar for a city: per-day Gregorian and Hijri (Islamic calendar) dates with salah times (Fajr, Dhuhr, Maghrib, Isha).
AI agents call hijri_calendar to retrieve information from Mcp Prayer Times without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | Yes | City name, e.g. "London". |
year | number | Yes | Gregorian year, e.g. 2026. |
month | number | Yes | Gregorian month, 1-12. |
method | number | — | Prayer-time calculation method. Default 2 = ISNA; 3 = MWL; 4 = Umm al-Qura; and others. |
country | string | Yes | Country name or code, e.g. "UK". |
Parameters from the server's own tool schema.
This tool only retrieves and queries prayer time information from the Aladhan API. It returns read-only calendar data (dates and prayer times) without any side effects, data modification, or external operations. The severity is low as misuse poses minimal risk - the worst outcome would be retrieving incorrect prayer times for a location, which has no security, financial, or operational impact.
From the tool's definition Tool description states it provides 'Monthly Islamic prayer-times calendar for a city: per-day Gregorian and Hijri (Islamic calendar) dates with salah times' - purely retrieving and displaying calendar and prayer time data with no modification, deletion, or…
Attacks that exploit this kind of access
Monthly Islamic prayer-times calendar for a city: per-day Gregorian and Hijri (Islamic calendar) dates with salah times (Fajr, Dhuhr, Maghrib, Isha). It is categorised as a Read tool in the Mcp Prayer Times MCP Server, which means it retrieves data without modifying state.
hijri_calendar accepts 5 parameters: city, year, month, method, country. Required: city, year, month, country. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Prayer Times MCP server in PolicyLayer and add a rule for hijri_calendar: 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 Mcp Prayer Times. Nothing to install.
hijri_calendar 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 hijri_calendar 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 hijri_calendar. 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.
hijri_calendar is provided by the Mcp Prayer Times MCP server (pipeworx-io/mcp-prayer-times). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →