AI agents call quran_ayah to retrieve information from MCP-Dubai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns Quranic text based on chapter and verse parameters. It is a read-only operation that queries public religious data without creating, modifying, deleting, executing code, or committing financial transactions. The blast radius of misuse is negligible—returning unwanted Quranic verses poses no security, privacy, or operational risk.
From the tool's definition Tool retrieves a single Quranic verse by reference (e.g., '2:255'). The description indicates a query operation with no side effects: 'Get a single ayah by reference.'
Attacks that exploit this kind of access
Get a single ayah by reference (e.g., "2:255" for Ayat al-Kursi). It is categorised as a Read tool in the MCP-Dubai MCP Server, which means it retrieves data without modifying state.
Register the MCP-Dubai MCP server in PolicyLayer and add a rule for quran_ayah: 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-Dubai. Nothing to install.
quran_ayah 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 quran_ayah 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 quran_ayah. 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.
quran_ayah is provided by the MCP-Dubai MCP server (mahdi-salmanzade/mcp-dubai). 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 →