Low Risk

advanced_search

Advanced search with sorting and filtering capabilities.

How to control advanced_search ↓

What advanced_search does on Alfresco MCP Server

AI agents call advanced_search to retrieve information from Alfresco MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why advanced_search needs a policy

This tool performs search operations on a document management system with sorting and filtering—classic read-only operations that retrieve data without side effects. The context as a content management platform and sibling tools (browse_repository, get_node_properties) reinforce this is a retrieval function. No creation, modification, deletion, code execution, or financial impact is indicated.

From the tool's definition Tool name 'advanced_search' combined with description 'Advanced search with sorting and filtering capabilities' indicates a query/retrieval operation with no data modification.

Documented attack patterns abuse exactly the kind of access advanced_search gives an agent:

How to control advanced_search

PolicyLayer is an MCP gateway — it sits between your AI agents and Alfresco MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for advanced_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "advanced_search": {}
  }
}

advanced_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Alfresco MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about advanced_search

What does the advanced_search tool do? +

Advanced search with sorting and filtering capabilities. It is categorised as a Read tool in the Alfresco MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on advanced_search? +

Register the Alfresco MCP Server MCP server in PolicyLayer and add a rule for advanced_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 Alfresco MCP Server. Nothing to install.

What risk level is advanced_search? +

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

Can I rate-limit advanced_search? +

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

How do I block advanced_search completely? +

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

What MCP server provides advanced_search? +

advanced_search is provided by the Alfresco MCP Server MCP server (stevereiner/python-alfresco-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Alfresco MCP Server tool call.

Start from Alfresco MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 Alfresco MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.