Get available locales for a site and language master
AI agents call fetchAvailableLocales to retrieve information from AEM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves locale information from an AEM site configuration. It performs no mutations, deletions, code execution, or financial operations. The verb 'fetch' and action 'get' are characteristic of Read operations. The blast radius of misuse is minimal—an AI agent could only retrieve metadata about available locales, which is non-sensitive configuration data in most contexts.
From the tool's definition Tool name 'fetchAvailableLocales' and description 'Get available locales for a site and language master' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get available locales for a site and language master. It is categorised as a Read tool in the AEM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AEM MCP Server MCP server in PolicyLayer and add a rule for fetchAvailableLocales: 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 AEM MCP Server. Nothing to install.
fetchAvailableLocales 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 fetchAvailableLocales 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 fetchAvailableLocales. 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.
fetchAvailableLocales is provided by the AEM MCP Server MCP server (udaykumarbpatel/aem-mcp-server). 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 →