Obtenir les mots-clés associés.
AI agents call get_keywords_related 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 performs a data retrieval operation typical of SEO analysis tools. It fetches related keywords based on input parameters, which is a read-only operation with no side effects, no code execution, and no data modification or deletion. The low severity reflects that misuse would only expose keyword research data, with minimal blast radius for an AI agent.
From the tool's definition Tool name 'get_keywords_related' and description 'Obtenir les mots-clés associés' (Obtain related keywords) indicate a retrieval operation that queries keyword data from the Haloscan SEO API without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Obtenir les mots-clés associés. 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_keywords_related: 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_keywords_related 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_keywords_related 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_keywords_related. 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_keywords_related 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 →