Low Risk

listRecentChanges

List recent changes across all projects in Weblate

How to control listRecentChanges ↓

What listRecentChanges does on Weblate MCP Server

AI agents call listRecentChanges 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 listRecentChanges needs a policy

This tool retrieves and queries change history metadata across projects. It has no side effects, does not modify data, and does not execute external operations. It is a straightforward read/query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'listRecentChanges' and description 'List recent changes across all projects in Weblate' indicate retrieval of historical data without modification. The verb 'list' is a canonical read operation.

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

How to control listRecentChanges

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 listRecentChanges:

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

listRecentChanges 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 listRecentChanges

What does the listRecentChanges tool do? +

List recent changes across all projects in 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 listRecentChanges? +

Register the Weblate MCP Server MCP server in PolicyLayer and add a rule for listRecentChanges: 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 listRecentChanges? +

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

Can I rate-limit listRecentChanges? +

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

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

listRecentChanges 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.