Obtenir l’historique des positions des domaines.
AI agents call get_domains_history_pages to retrieve information from Haloscan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical domain ranking position data without creating, modifying, deleting, or executing any operations. It fits the Read category: retrieves data with no side effects. The severity is low because accessing historical SEO data poses minimal risk—it is informational only and cannot be weaponized to cause harm or unauthorized changes to systems or data.
From the tool's definition Tool name 'get_domains_history_pages' and description 'Obtenir l'historique des positions des domaines' (Get domain position history) indicate retrieval of historical ranking data.
Attacks that exploit this kind of access
Obtenir l’historique des positions des domaines. It is categorised as a Read tool in the Haloscan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Haloscan MCP Server MCP server in PolicyLayer and add a rule for get_domains_history_pages: 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 Haloscan MCP Server. Nothing to install.
get_domains_history_pages 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_domains_history_pages 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_domains_history_pages. 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_domains_history_pages is provided by the Haloscan MCP Server MCP server (occirank/haloscan-mcp-server). 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 →