find_collocations
AI agents call find_collocations to retrieve information from DHLAB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Collocations analysis is a standard corpus linguistics operation that retrieves and analyzes word frequency and association data from existing text collections. Like its sibling tools (concordance, ngram, word lookup, corpus statistics), it queries and returns analytical data without modifying, executing code, or causing side effects.
From the tool's definition Tool named 'find_collocations' with empty description, but contextually situated among other read-only corpus analysis tools (find_concordances, get_corpus_statistics, lookup_word_forms, ngram_frequencies, search_texts).
Attacks that exploit this kind of access
find_collocations. It is categorised as a Read tool in the DHLAB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DHLAB MCP Server MCP server in PolicyLayer and add a rule for find_collocations: 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 DHLAB MCP Server. Nothing to install.
find_collocations 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 find_collocations 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 find_collocations. 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.
find_collocations is provided by the DHLAB MCP Server MCP server (marksverdhei/dhlab-mcp). 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 →