Obtenir l’historique des positions des domaines.
AI agents call get_domains_history_positions 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 queries and retrieves historical ranking position data for domains from the Haloscan SEO API. It has no side effects—it does not modify, delete, or execute operations. It is a read-only data retrieval function consistent with the server's purpose of SEO analysis and research.
From the tool's definition Tool name 'get_domains_history_positions' and description 'Obtenir l'historique des positions des domaines' (Get the history of domain positions) indicate retrieval of historical SEO 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_positions: 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_positions 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_positions 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_positions. 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_positions 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 →