list_recent_changes_tool
AI agents call list_recent_changes_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.
Despite the empty description, the tool name clearly indicates it retrieves historical change data without modifying it. This is a read-only query operation. Confidence is slightly reduced due to the missing description, but the naming convention is unambiguous. The severity is low as it only exposes existing, non-sensitive metadata that wikis typically make publicly available.
From the tool's definition Tool name 'list_recent_changes_tool' indicates retrieval of recent changes data from MediaWiki. The verb 'list' and pattern matching sibling tools (get_page_tool, get_category_members_tool, get_file_info_tool) which are read-only operations confirm this is a…
Attacks that exploit this kind of access
list_recent_changes_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_recent_changes_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_recent_changes_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_recent_changes_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_recent_changes_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_recent_changes_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 →