This record as markdown: /tools/mcp-dev/get-log-viewer-saved-search.md
What get-log-viewer-saved-search does on Mcp Dev
AI agents call get-log-viewer-saved-search 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-log-viewer-saved-search is rated Low
This tool retrieves saved log viewer searches from Umbraco CMS, which is a read-only operation with no side effects. It merely fetches and returns data that already exists. There is minimal risk of misuse as it cannot modify, delete, or execute operations.
From the tool's definition Tool name is 'get-log-viewer-saved-search' and description states 'Get log viewer saved searches'. The verb 'get' indicates retrieval of existing log search configurations without modification.
Attacks that exploit this kind of access
The rule that runs get-log-viewer-saved-search 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-saved-search, this is the rule to start with:
get-log-viewer-saved-search 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-log-viewer-saved-search call is checked against it from then on.
Questions about get-log-viewer-saved-search
Get log viewer saved searches. 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-log-viewer-saved-search: 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-log-viewer-saved-search 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-log-viewer-saved-search 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-log-viewer-saved-search. 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-log-viewer-saved-search 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