Count Wikipedia edits for a time window (YYYYMMDDHHmmss).
AI agents call get_revert_counts to retrieve information from Wikicitation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and counts historical revert data from Wikipedia within a specified time window. It has no side effects—it does not create, modify, delete, or execute any actions. The operation is purely informational and read-only, consistent with other sibling tools on the server like 'get_article_history' and 'get_any_count'. No blast radius from accidental misuse by an AI agent.
From the tool's definition Tool name 'get_revert_counts' and description 'Count Wikipedia edits for a time window' indicate a query/retrieval operation that counts revert actions without modifying any data.
Attacks that exploit this kind of access
Count Wikipedia edits for a time window (YYYYMMDDHHmmss). It is categorised as a Read tool in the Wikicitation MCP Server, which means it retrieves data without modifying state.
Register the Wikicitation MCP server in PolicyLayer and add a rule for get_revert_counts: 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 Wikicitation. Nothing to install.
get_revert_counts 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_revert_counts 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_revert_counts. 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_revert_counts is provided by the Wikicitation MCP server (jsobel1/wikicitation-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 →