search_datanexus_tools
Find the right DataNexus tool by describing your task in plain English. Read-only. No side effects. Call this before any other DataNexus tool to reduce context load from 40000 to 800 tokens. query: Plain English description of your task e.g. check if a Python package has CVEs or look up a UK char...
This record as markdown: /tools/dev-7bd0-mcp-server/search-datanexus-tools.md
What search_datanexus_tools does on DataNexus MCP
AI agents call search_datanexus_tools to retrieve information from DataNexus MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | Plain English description of your task, e.g. 'check if a Python package has CVEs' or 'look up a UK charity by name'. Required. |
domain | object | — | Restrict results to one sub-server: nonprofit, security, compliance, domain, legal, govcon, or regulatory. Optional. |
Parameters from the server's own tool schema.
Why search_datanexus_tools is rated Low
This is a discovery/search tool that retrieves metadata about available tools without modifying, executing, or deleting anything. It helps users find appropriate tools by matching descriptions, making it a pure read operation with no side effects or blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states "Read-only. No side effects." It performs search/discovery functionality to "Find the right DataNexus tool" and "Returns matching tool names and parameter hints."
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs search_datanexus_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_datanexus_tools, this is the rule to start with:
search_datanexus_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every search_datanexus_tools call is checked against it from then on.
Questions about search_datanexus_tools
Find the right DataNexus tool by describing your task in plain English. Read-only. No side effects. Call this before any other DataNexus tool to reduce context load from 40000 to 800 tokens. query: Plain English description of your task e.g. check if a Python package has CVEs or look up a UK charity by name. Required. domain: Restrict results to one sub-server: nonprofit, security, compliance, domain, legal, govcon, or regulatory. Optional. Returns matching tool names and parameter hints you can call directly. Do not call this recursively or to validate results — use validate_tool_output for that. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="search_datanexus_tools", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
search_datanexus_tools accepts 2 parameters: query, domain. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for search_datanexus_tools: 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 DataNexus MCP. Nothing to install.
search_datanexus_tools 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 search_datanexus_tools 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 search_datanexus_tools. 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.
search_datanexus_tools is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue