get_recent_changes
AI agents call get_recent_changes to retrieve information from WikiJS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context indicate this retrieves historical data about recent changes to wiki pages. No creation, modification, deletion, code execution, or financial operations are implied. The empty description lowers confidence slightly, but the 'get_' prefix and context of sibling tools (get_wiki_page, get_wiki_stats, get_page_history) confirm this is a retrieval operation with no side effects.
From the tool's definition Tool name 'get_recent_changes' and server description indicating 'retrieval of wiki statistics' and 'knowledge graph exploration' suggest a read-only query operation. The tool appears designed to fetch change logs or recent activity data without modification.
Attacks that exploit this kind of access
get_recent_changes. It is categorised as a Read tool in the WikiJS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WikiJS MCP Server MCP server in PolicyLayer and add a rule for get_recent_changes: 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 WikiJS MCP Server. Nothing to install.
get_recent_changes 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 get_recent_changes 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 get_recent_changes. 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.
get_recent_changes is provided by the WikiJS MCP Server MCP server (vnikhilbuddhavarapu/wiki-mcp). 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 →