This record as markdown: /tools/0xchamin-mcptube/wiki-history.md
What wiki_history does on Mcptube Vision
AI agents call wiki_history to retrieve information from Mcptube Vision without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wiki_history is rated Low
This tool retrieves and displays version history information about a wiki page. It performs no side effects, creates no new data, executes no code, and causes no irreversible changes. Version history viewing is a fundamental read operation with minimal security risk, as it only exposes information already stored in the system.
From the tool's definition Tool name 'wiki_history' and description 'View version history for a wiki page' indicate retrieval of historical metadata without modification or deletion. The verb 'View' is a read-only operation.
Attacks that exploit this kind of access
The rule that runs wiki_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcptube Vision, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wiki_history, this is the rule to start with:
wiki_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcptube Vision, apply this rule, and every wiki_history call is checked against it from then on.
Questions about wiki_history
View version history for a wiki page. It is categorised as a Read tool in the Mcptube Vision MCP Server, which means it retrieves data without modifying state.
Register the Mcptube Vision MCP server in PolicyLayer and add a rule for wiki_history: 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 Mcptube Vision. Nothing to install.
wiki_history 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 wiki_history 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 wiki_history. 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.
wiki_history is provided by the Mcptube Vision MCP server (0xchamin/mcptube). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcptube Vision, and thousands of servers like it.
This server
Across the catalogue