getChangesByUser

THE RISK

Low Risk

Why getChangesByUser needs a policy

This tool retrieves historical change data for audit or reporting purposes. It has no side effects, does not modify any translations or project state, and poses minimal risk if called by an AI agent. The read-only nature and the context of other tools on the server (which include write/bulk operations as separate tools) confirm this is purely informational.

From the tool's definition Tool name 'getChangesByUser' and description 'Get recent changes by a specific user' indicate a retrieval operation with no modification capability.

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

POLICY

How to control getChangesByUser

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getChangesByUser": {}
  }
}

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

Create a free account and register Weblate MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Weblate MCP Server tools

Write bulkWriteTranslations Update multiple translations in batch for efficient bulk operations Write writeTranslation Update or write a translation value for a specific key Read findTranslationsForKey Find all translations for a specific key across all components and languages in a project Read getComponentChanges Get recent changes for a specific component Read getComponentLanguageProgress Get translation progress for all languages in a component Read getComponentStatistics Get detailed statistics for a specific component Read getLanguageStatistics Get statistics for a specific language across all projects Read getProjectChanges Get recent changes for a specific project

All 20 Weblate MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getChangesByUser

What does the getChangesByUser tool do? +

Get recent changes by a specific user. 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 getChangesByUser? +

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

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

Can I rate-limit getChangesByUser? +

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

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

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

CHECK YOUR STACK →