get-log-viewer-level

Get log viewer levels

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-log-viewer-level.md

WHAT IT DOES

What get-log-viewer-level does on Mcp Dev

AI agents call get-log-viewer-level 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-log-viewer-level is rated Low

This tool retrieves log viewer levels from the Umbraco CMS system. It performs no data modification, deletion, code execution, or financial operations. The operation is read-only and retrieving system configuration data has minimal blast radius if misused by an AI agent, as it only exposes existing logging level settings without side effects.

From the tool's definition Tool name 'get-log-viewer-level' and description 'Get log viewer levels' indicate a retrieval operation that queries existing log viewer configuration without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get-log-viewer-level Allowed

get-log-viewer-level 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-log-viewer-level": {}
  }
}

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-log-viewer-level call is checked against it from then on.

FAQ

Questions about get-log-viewer-level

What does the get-log-viewer-level tool do? +

Get log viewer levels. 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-log-viewer-level? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-log-viewer-level: 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-log-viewer-level? +

get-log-viewer-level is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-log-viewer-level? +

Yes. Add a rate_limit block to the get-log-viewer-level 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-log-viewer-level completely? +

Set action: deny in the PolicyLayer policy for get-log-viewer-level. 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-log-viewer-level? +

get-log-viewer-level 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 →