Get a comprehensive dashboard overview for a project with all component statistics
AI agents call getProjectDashboard 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.
This tool retrieves and presents aggregated statistics and overview information about a translation project. It performs no write, delete, or execute operations—it simply queries and returns existing data for display purposes. The read-only nature and lack of side effects place it squarely in the Read category with low severity.
From the tool's definition Tool name 'getProjectDashboard' and description 'Get a comprehensive dashboard overview for a project with all component statistics' indicate data retrieval with no modification. The verb 'Get' and lack of any mutation language confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access getProjectDashboard gives an agent:
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 getProjectDashboard:
{
"version": "1",
"default": "deny",
"tools": {
"getProjectDashboard": {}
}
} getProjectDashboard is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a comprehensive dashboard overview for a project with all component statistics. It is categorised as a Read tool in the Weblate MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weblate MCP Server MCP server in PolicyLayer and add a rule for getProjectDashboard: 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.
getProjectDashboard is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getProjectDashboard 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.
Set action: deny in the PolicyLayer policy for getProjectDashboard. 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.
getProjectDashboard 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.
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.