Low Risk

searchUnitsWithFilters

Search translation units using Weblate\

How to control searchUnitsWithFilters ↓

What searchUnitsWithFilters does on Weblate MCP Server

AI agents call searchUnitsWithFilters to retrieve information from Weblate 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 searchUnitsWithFilters needs a policy

This tool retrieves or queries translation units from Weblate based on filter criteria with no side effects. It is a read-only operation consistent with the other analytics and retrieval tools on the server.

From the tool's definition Tool name contains 'search' and description states 'Search translation units'. The sibling tools include 'find', 'get', and 'getChangesByUser' which are all read-only operations. No write, execute, or destructive capabilities are implied.

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

How to control searchUnitsWithFilters

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

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

searchUnitsWithFilters 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 Weblate 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 searchUnitsWithFilters

What does the searchUnitsWithFilters tool do? +

Search translation units using Weblate\. It is categorised as a Read tool in the Weblate MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searchUnitsWithFilters? +

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

What risk level is searchUnitsWithFilters? +

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

Can I rate-limit searchUnitsWithFilters? +

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

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

searchUnitsWithFilters is provided by the Weblate MCP Server MCP server (mmntm/weblate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Weblate MCP Server tool call.

Start from Weblate 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.

20 Weblate 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.