Low Risk

search_with_progress

search_with_progress

How to control search_with_progress ↓

What search_with_progress does on OLEXI Australian Laws MCP Server

AI agents call search_with_progress to retrieve information from OLEXI Australian Laws 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 search_with_progress needs a policy

This tool retrieves legal documents from AustLII without modifying data or executing arbitrary operations. The empty description lowers confidence slightly, but the server's stated function (searching and finding documents) and sibling tools (build_search_url, list_databases, search_austlii) all point to read-only search operations. No side effects or destructive actions are indicated.

From the tool's definition Tool name 'search_with_progress' combined with server context (searches AustLII for legislation and case law) indicates a retrieval operation.

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

How to control search_with_progress

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

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

search_with_progress 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 OLEXI Australian Laws 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 search_with_progress

What does the search_with_progress tool do? +

search_with_progress. It is categorised as a Read tool in the OLEXI Australian Laws MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_with_progress? +

Register the OLEXI Australian Laws MCP Server MCP server in PolicyLayer and add a rule for search_with_progress: 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 OLEXI Australian Laws MCP Server. Nothing to install.

What risk level is search_with_progress? +

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

Can I rate-limit search_with_progress? +

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

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

search_with_progress is provided by the OLEXI Australian Laws MCP Server MCP server (konashevich/olexi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OLEXI Australian Laws MCP Server tool call.

Start from OLEXI Australian Laws 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.

4 OLEXI Australian Laws 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.