cms_search_entries

Hybrid full-text + semantic search across CMS entries. Each hit carries a match excerpt, the derived title, and summarized field data — long text is shortened to a lead with a word count in

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/cms-search-entries.md

WHAT IT DOES

What cms_search_entries does on Munin

AI agents call cms_search_entries to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why cms_search_entries is rated Low

Tool queries and retrieves CMS content with no side effects or data modification capability.

From the tool's definition search across CMS entries, match excerpt, field data — retrieves information only

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cms_search_entries safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cms_search_entries, this is the rule to start with:

cms_search_entries Allowed

cms_search_entries 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": {
    "cms_search_entries": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every cms_search_entries call is checked against it from then on.

FAQ

Questions about cms_search_entries

What does the cms_search_entries tool do? +

Hybrid full-text + semantic search across CMS entries. Each hit carries a match excerpt, the derived title, and summarized field data — long text is shortened to a lead with a word count in. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cms_search_entries? +

Register the Munin MCP server in PolicyLayer and add a rule for cms_search_entries: 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 Munin. Nothing to install.

What risk level is cms_search_entries? +

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

Can I rate-limit cms_search_entries? +

Yes. Add a rate_limit block to the cms_search_entries 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 cms_search_entries completely? +

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

cms_search_entries is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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