openfigi_search
Search OpenFIGI for financial instruments by name.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/openfigi-search.md
What openfigi_search does on UnClick
AI agents call openfigi_search to retrieve information from UnClick 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 | Search query (company or instrument name). |
Parameters from the server's own tool schema.
Why openfigi_search is rated Low
This is a read-only operation that queries a financial database (OpenFIGI, a public reference system for global financial instrument identifiers). It retrieves information for lookup purposes only, with no side effects, execution of code, modifications to accounts, or financial transactions. The 'search' verb and lack of action verbs (pay, transfer, trade, delete, execute) confirm it is purely informational.
From the tool's definition The tool name 'openfigi_search' and description 'Search OpenFIGI for financial instruments by name' indicate a search/query operation that retrieves data about financial instruments without modifying, executing transactions, or creating financial obligations.
Attacks that exploit this kind of access
The rule that runs openfigi_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openfigi_search, this is the rule to start with:
openfigi_search 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 UnClick, apply this rule, and every openfigi_search call is checked against it from then on.
Questions about openfigi_search
Search OpenFIGI for financial instruments by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
openfigi_search accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for openfigi_search: 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 UnClick. Nothing to install.
openfigi_search 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 openfigi_search 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 openfigi_search. 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.
openfigi_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue