Resolve free text to a canonical market or macro entity. Turns a ticker, company name, macro indicator, coin, or currency pair into the agent plane's {namespace, ids} entity for use with get_snapshot and get_timeseries. A cross-namespace collision (e.g. a ticker that is both an equity and a coin)...
AI agents call resolve_entity to retrieve information from Sugra API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | |
type_hint | object | — |
Parameters from the server's own tool schema.
This tool performs a lookup/resolution operation, converting free-text identifiers into canonical entity references. It only retrieves and returns data (namespace and IDs), with no side effects, modifications, or destructive actions. It is purely a read/query operation with minimal blast radius if misused.
From the tool's definition Resolve free text to a canonical market or macro entity... Turns a ticker, company name, macro indicator, coin, or currency pair into the agent plane's {namespace, ids} entity
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Resolve free text to a canonical market or macro entity. Turns a ticker, company name, macro indicator, coin, or currency pair into the agent plane's {namespace, ids} entity for use with get_snapshot and get_timeseries. A cross-namespace collision (e.g. a ticker that is both an equity and a coin) returns status "ambiguous" with ranked candidates and NEVER silently picks one; pass type_hint (e.g. "equity", "etf", "coin") to narrow the universe. For compliance KYB lookups by LEI/VAT or sanctions screening use sugra_entity_lookup / sugra_entity_screen instead - this tool is for market-data entities. Args: query: Free-form text - ticker, company, indicator, coin, or pair. type_hint: Optional namespace hint narrowing resolution. It is categorised as a Read tool in the Sugra API MCP Server, which means it retrieves data without modifying state.
resolve_entity accepts 2 parameters: query, type_hint. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Sugra API MCP server in PolicyLayer and add a rule for resolve_entity: 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 Sugra API. Nothing to install.
resolve_entity 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 resolve_entity 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 resolve_entity. 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.
resolve_entity is provided by the Sugra API MCP server (pypi:sugra-api-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 →