AI agents call gregorian_to_hijri 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 is a stateless date conversion function. It takes a Gregorian date as input and returns the equivalent Hijri date. No data is created, modified, deleted, or executed. No external operations are triggered. The tool has no blast radius if misused by an AI agent—worst case, it returns an incorrect date conversion. This clearly falls under the Read category as a data transformation/lookup operation.
From the tool's definition Tool name 'gregorian_to_hijri' and description 'Convert a Gregorian date to a Hijri (Islamic) date' indicate a pure date conversion utility that retrieves or transforms a calendar input with no side effects, data modification, execution, deletion, or…
Attacks that exploit this kind of access
Convert a Gregorian date to a Hijri (Islamic) date. 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 gregorian_to_hijri: 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.
gregorian_to_hijri 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 gregorian_to_hijri 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 gregorian_to_hijri. 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.
gregorian_to_hijri 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 →