Search for assistants by name
AI agents call search_assistants_by_name to retrieve information from Dust 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 or queries data about assistants based on name criteria. It performs a read-only search operation with no ability to modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could only discover available assistants, which is informational. No data is created, modified, deleted, or executed.
From the tool's definition The tool name 'search_assistants_by_name' and description 'Search for assistants by name' indicate a query/retrieval operation with no modification or execution capability. This is a classic search/lookup function that retrieves data without side effects.
Attacks that exploit this kind of access
Search for assistants by name. It is categorised as a Read tool in the Dust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dust MCP Server MCP server in PolicyLayer and add a rule for search_assistants_by_name: 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 Dust MCP Server. Nothing to install.
search_assistants_by_name 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_assistants_by_name 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_assistants_by_name. 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_assistants_by_name is provided by the Dust MCP Server MCP server (ma3u/dust-mcp-server-postman-railway). 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 →