list_user_contributions_tool
AI agents call list_user_contributions_tool to retrieve information from MCP Mediawiki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user contribution history without modifying data. The lack of description reduces confidence slightly, but the naming convention clearly indicates a read-only operation that lists/retrieves existing data. User contribution lists are typically non-sensitive in public wikis and commonly queried for auditing purposes.
From the tool's definition Tool name 'list_user_contributions_tool' indicates it retrieves historical user activity records from MediaWiki. The server description emphasizes 'search, pages, categories, and more' with no destructive operations mentioned for this tool.
Attacks that exploit this kind of access
list_user_contributions_tool. It is categorised as a Read tool in the MCP Mediawiki MCP Server, which means it retrieves data without modifying state.
Register the MCP Mediawiki MCP server in PolicyLayer and add a rule for list_user_contributions_tool: 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 MCP Mediawiki. Nothing to install.
list_user_contributions_tool 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 list_user_contributions_tool 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 list_user_contributions_tool. 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.
list_user_contributions_tool is provided by the MCP Mediawiki MCP server (mcp-mediawiki-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →