get-element-configuration

Gets the element configuration for the Umbraco instance.

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/get-element-configuration.md

WHAT IT DOES

What get-element-configuration does on Mcp Dev

AI agents call get-element-configuration 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.

RISK

Why get-element-configuration is rated Low

This tool retrieves configuration information about elements in an Umbraco CMS instance. The 'get' verb and passive retrieval of existing configuration data clearly indicates a Read operation. No data is modified, deleted, or executed—only queried. The blast radius of misuse is minimal, as reading configuration poses no integrity or availability risk to the system.

From the tool's definition Tool name 'get-element-configuration' and description 'Gets the element configuration' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-element-configuration 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-element-configuration, this is the rule to start with:

get-element-configuration Allowed

get-element-configuration is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-element-configuration": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every get-element-configuration call is checked against it from then on.

FAQ

Questions about get-element-configuration

What does the get-element-configuration tool do? +

Gets the element configuration for the Umbraco instance. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-element-configuration? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-element-configuration: 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.

What risk level is get-element-configuration? +

get-element-configuration is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-element-configuration? +

Yes. Add a rate_limit block to the get-element-configuration 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.

How do I block get-element-configuration completely? +

Set action: deny in the PolicyLayer policy for get-element-configuration. 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.

What MCP server provides get-element-configuration? +

get-element-configuration 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.

KEEP EXPLORING

More on Mcp Dev, and thousands of servers like it.

This server

All 419 Mcp Dev tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →