This record as markdown: /tools/3ilm-mcp/search-vulnerabilities.md
What search_vulnerabilities does on 3ilm
AI agents call search_vulnerabilities to retrieve information from 3ilm 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 | Yes | Keyword search query. Examples: "oracle price manipulation", "reentrancy", "fee calculation", "flash loan", "access control", "rounding error" |
Parameters from the server's own tool schema.
Why search_vulnerabilities is rated Low
Search operations retrieve and query data without modifying state or triggering external actions. The lack of language suggesting creation, deletion, execution, or financial impact places this firmly in the Read category. Severity is low because unauthorized vulnerability data queries, while undesirable, do not directly cause damage compared to destructive or executable tools.
From the tool's definition Tool name 'search_vulnerabilities' indicates a query/search operation. The verb 'search' is typical of retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs search_vulnerabilities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3ilm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_vulnerabilities, this is the rule to start with:
search_vulnerabilities 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 3ilm, apply this rule, and every search_vulnerabilities call is checked against it from then on.
Questions about search_vulnerabilities
search_vulnerabilities is a read tool on the 3ilm MCP server. It is categorised as a Read tool in the 3ilm MCP Server, which means it retrieves data without modifying state.
search_vulnerabilities accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the 3ilm MCP server in PolicyLayer and add a rule for search_vulnerabilities: 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 3ilm. Nothing to install.
search_vulnerabilities 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_vulnerabilities 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_vulnerabilities. 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_vulnerabilities is provided by the 3ilm MCP server (3ilm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3ilm, and thousands of servers like it.
This server
Across the catalogue