Get the next upcoming prayer time for a Moroccan city
AI agents call get_next_prayer to retrieve information from Morocco Open Data MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns prayer time information for a specified city. It is a straightforward read operation that retrieves existing data without creating, modifying, deleting, executing code, or involving financial transactions. The low severity reflects minimal risk if misused—an AI agent could only retrieve prayer times, which is public religious scheduling information.
From the tool's definition Tool name 'get_next_prayer' and description 'Get the next upcoming prayer time for a Moroccan city' indicate a pure data retrieval operation with no side effects or modifications.
Attacks that exploit this kind of access
Get the next upcoming prayer time for a Moroccan city. It is categorised as a Read tool in the Morocco Open Data MCP MCP Server, which means it retrieves data without modifying state.
Register the Morocco Open Data MCP server in PolicyLayer and add a rule for get_next_prayer: 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 Morocco Open Data MCP. Nothing to install.
get_next_prayer 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_next_prayer 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_next_prayer. 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_next_prayer is provided by the Morocco Open Data MCP server (kcbdev/morocco-open-data-mcp). 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 →