List all revisions of a Docs article
AI agents call docs_list_revisions to retrieve information from MCP Help Scout without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of article revision history. It retrieves information about past versions of a document but does not create, modify, delete, or execute any operations. The action is passive data retrieval with no side effects, clearly falling into the Read category with low severity since it only exposes historical metadata.
From the tool's definition Tool name 'docs_list_revisions' and description 'List all revisions of a Docs article' indicate a retrieval operation that queries historical versions of an article without modifying or deleting data.
Attacks that exploit this kind of access
List all revisions of a Docs article. It is categorised as a Read tool in the MCP Help Scout MCP Server, which means it retrieves data without modifying state.
Register the MCP Help Scout MCP server in PolicyLayer and add a rule for docs_list_revisions: 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 Help Scout. Nothing to install.
docs_list_revisions 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 docs_list_revisions 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 docs_list_revisions. 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.
docs_list_revisions is provided by the MCP Help Scout MCP server (solveitsimply/mcp-helpscout). 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 →