get-culture
Retrieves a paginated list of cultures that Umbraco can be configured to use
This record as markdown: /tools/mcp-dev/get-culture.md
What get-culture does on Mcp Dev
AI agents call get-culture to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-culture is rated Low
This tool retrieves configuration data (available cultures) without side effects. It is a standard data query operation that does not create, modify, delete, or execute any code. The paginated list retrieval is a typical Read operation with minimal risk.
From the tool's definition Tool name 'get-culture' and description 'Retrieves a paginated list of cultures' indicate a read-only query operation with no data modification or execution capability.
Attacks that exploit this kind of access
The rule that runs get-culture safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-culture, this is the rule to start with:
get-culture is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every get-culture call is checked against it from then on.
Questions about get-culture
Retrieves a paginated list of cultures that Umbraco can be configured to use. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-culture: 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 Dev. Nothing to install.
get-culture 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-culture 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-culture. 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-culture is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue