check_page_history
AI agents call check_page_history to retrieve information from Backlink SEO without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve historical information about a page's links, mentions, or content without modifying external systems. While the description is empty, the naming convention and server's stated purpose (surfacing data, narrowing angles, verifying links) strongly indicate this is a data retrieval tool. No side effects, no state changes.
From the tool's definition Tool name 'check_page_history' and server context indicate querying historical page data. The broader server provides 'surface pages that mention a brand', 'see who links to competitors', and 'verify whether a page links to you'—all read operations on…
Attacks that exploit this kind of access
check_page_history. It is categorised as a Read tool in the Backlink SEO MCP Server, which means it retrieves data without modifying state.
Register the Backlink SEO MCP server in PolicyLayer and add a rule for check_page_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 Backlink SEO. Nothing to install.
check_page_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 check_page_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 check_page_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.
check_page_history is provided by the Backlink SEO MCP server (vipulawl/mcp-backlink-for-seo). 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 →